Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f8b097f0eb3ab55e6eb4fca90382af52b000fbd0324ca73ccf90af8e78d976a

Tx prefix hash: e07a2f258586b74073474b031df626cce00239aabf71f0d98b20f3da69f6d6ca
Tx public key: d4176652dbf5e48f9553c616e2cc1b045defa6c29dcb233251d4e2039921c788
Timestamp: 1711213144 Timestamp [UCT]: 2024-03-23 16:59:04 Age [y:d:h:m:s]: 01:311:13:31:21
Block: 984730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481274 RingCT/type: yes/0
Extra: 01d4176652dbf5e48f9553c616e2cc1b045defa6c29dcb233251d4e2039921c78802110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0cfe3d78ae0bfd4fbac928367c3be645effff42ffc32c2070516c3b1179e059 0.600000000000 1444903 of 15

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": 984740, "vin": [ { "gen": { "height": 984730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0cfe3d78ae0bfd4fbac928367c3be645effff42ffc32c2070516c3b1179e059" } } ], "extra": [ 1, 212, 23, 102, 82, 219, 245, 228, 143, 149, 83, 198, 22, 226, 204, 27, 4, 93, 239, 166, 194, 157, 203, 35, 50, 81, 212, 226, 3, 153, 33, 199, 136, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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