Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e691d2c402a05fadf33fba3647f28c3ccb84df91bc5d28fe48f92c11a660ce

Tx prefix hash: 2954464b61aeca80fd05dfd2944ac626fae78b36009bf4a783234b806f7c5391
Tx public key: 934dcb72a7c68ff504c7cecbf0044fe6b9d06d08e1fc74302f89ca1249b1edf9
Timestamp: 1658356333 Timestamp [UCT]: 2022-07-20 22:32:13 Age [y:d:h:m:s]: 03:102:07:45:43
Block: 548140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 852885 RingCT/type: yes/0
Extra: 01934dcb72a7c68ff504c7cecbf0044fe6b9d06d08e1fc74302f89ca1249b1edf902110000000175e3f0e9000000000000000000

1 output(s) for total of 9.370974827000 dcy

stealth address amount amount idx
00: 54e6c6773fc88af96763d0a956e9c2c46a0f12f3e1474a7621f20c5391187a1c 9.370974827000 979363 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": 548150, "vin": [ { "gen": { "height": 548140 } } ], "vout": [ { "amount": 9370974827, "target": { "key": "54e6c6773fc88af96763d0a956e9c2c46a0f12f3e1474a7621f20c5391187a1c" } } ], "extra": [ 1, 147, 77, 203, 114, 167, 198, 143, 245, 4, 199, 206, 203, 240, 4, 79, 230, 185, 208, 109, 8, 225, 252, 116, 48, 47, 137, 202, 18, 73, 177, 237, 249, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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