Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f30ffe1ea60fb5a858e2b00b406ec27744271693d6228bc9a40c3ee2668fdb

Tx prefix hash: 942e737b2606d63a8ed82e2c1d8bd8d62fa705f9766d8dcaeebbd4f85254f36b
Tx public key: f2c2f87fff2abf6f9c893a2c48e97600b22fff51fe02b7b54e41a846c8d02e5a
Timestamp: 1703438941 Timestamp [UCT]: 2023-12-24 17:29:01 Age [y:d:h:m:s]: 01:328:04:47:20
Block: 920258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493413 RingCT/type: yes/0
Extra: 01f2c2f87fff2abf6f9c893a2c48e97600b22fff51fe02b7b54e41a846c8d02e5a02110000001259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf2dff01908d52f71e7e469242dedc049242f76cd0a98ceb328214840380f736 0.600000000000 1377936 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": 920268, "vin": [ { "gen": { "height": 920258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf2dff01908d52f71e7e469242dedc049242f76cd0a98ceb328214840380f736" } } ], "extra": [ 1, 242, 194, 248, 127, 255, 42, 191, 111, 156, 137, 58, 44, 72, 233, 118, 0, 178, 47, 255, 81, 254, 2, 183, 181, 78, 65, 168, 70, 200, 208, 46, 90, 2, 17, 0, 0, 0, 18, 89, 218, 211, 245, 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