Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e471b8b7b8496e2f97978651d55e1908abbc2eb481f0b34618a50d821409f1cd

Tx prefix hash: 973819729dc5935cdf96db1edf8eb59e11a0b609a7e0b7ea71b144de64d98c8b
Tx public key: 07491affb3d47bae462269edc21942f3c7c877abaa3f9d8a9cb5d4d110a1cfed
Timestamp: 1734651635 Timestamp [UCT]: 2024-12-19 23:40:35 Age [y:d:h:m:s]: 00:104:20:43:57
Block: 1178939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74700 RingCT/type: yes/0
Extra: 0107491affb3d47bae462269edc21942f3c7c877abaa3f9d8a9cb5d4d110a1cfed02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 097011894bbdad04c0b66dde9d3ea8955e30fab2bbc4140cdb36f97d0dd67ebc 0.600000000000 1665330 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": 1178949, "vin": [ { "gen": { "height": 1178939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097011894bbdad04c0b66dde9d3ea8955e30fab2bbc4140cdb36f97d0dd67ebc" } } ], "extra": [ 1, 7, 73, 26, 255, 179, 212, 123, 174, 70, 34, 105, 237, 194, 25, 66, 243, 199, 200, 119, 171, 170, 63, 157, 138, 156, 181, 212, 209, 16, 161, 207, 237, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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