Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf2c0f124b4318f18e8612e59f3d54252f7fdd5ae050e60c60db6b8d58d53748

Tx prefix hash: f77295ac1fa1fe22380dcc4fa46403ac071139d913572c4cc8004d2882caf648
Tx public key: b9f22dfd1d160e0d0ba3da866632f9af49a28ccbf95c14ad1d4cca60004bfa7c
Timestamp: 1704527747 Timestamp [UCT]: 2024-01-06 07:55:47 Age [y:d:h:m:s]: 01:161:12:59:15
Block: 929261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376516 RingCT/type: yes/0
Extra: 01b9f22dfd1d160e0d0ba3da866632f9af49a28ccbf95c14ad1d4cca60004bfa7c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12abf708aa9b3793446c3d0ce1645d2b096ac1b080e9e98b4817631e16a69dd9 0.600000000000 1387131 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": 929271, "vin": [ { "gen": { "height": 929261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12abf708aa9b3793446c3d0ce1645d2b096ac1b080e9e98b4817631e16a69dd9" } } ], "extra": [ 1, 185, 242, 45, 253, 29, 22, 14, 13, 11, 163, 218, 134, 102, 50, 249, 175, 73, 162, 140, 203, 249, 92, 20, 173, 29, 76, 202, 96, 0, 75, 250, 124, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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