Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a067bac6f7873e0f9fbe8997aab8f39fb1f19387d94949ce7b38a6cc567adbea

Tx prefix hash: ff8ebe7bd76e20a1a8c2f5759b0bc6360f020e63bdcaa4aa2462e38893fb2c2a
Tx public key: e56d7b913b937b7e79d12dc23bed734e5c4e96df85669fadc24dcf8316fea1d2
Timestamp: 1574525985 Timestamp [UCT]: 2019-11-23 16:19:45 Age [y:d:h:m:s]: 04:360:00:27:39
Block: 15704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1139373 RingCT/type: yes/0
Extra: 01e56d7b913b937b7e79d12dc23bed734e5c4e96df85669fadc24dcf8316fea1d2021100000002b63f0b49000000000000000000

1 output(s) for total of 544.461295361000 dcy

stealth address amount amount idx
00: 31c645a9ea832f57d024d18d26be514e8d442fdbb9ad308a73fd850e1d2cfa62 544.461295361000 21263 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 15714, "vin": [ { "gen": { "height": 15704 } } ], "vout": [ { "amount": 544461295361, "target": { "key": "31c645a9ea832f57d024d18d26be514e8d442fdbb9ad308a73fd850e1d2cfa62" } } ], "extra": [ 1, 229, 109, 123, 145, 59, 147, 123, 126, 121, 209, 45, 194, 59, 237, 115, 78, 92, 78, 150, 223, 133, 102, 159, 173, 194, 77, 207, 131, 22, 254, 161, 210, 2, 17, 0, 0, 0, 2, 182, 63, 11, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8