Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e9917d2155c41e4aa3d27dd008921f1379c3362092f1282afcd832f0b39c09

Tx prefix hash: 226c941cbd65f72baef66d1fd90bc401274235c8936c67afd51e10bc8d6211cf
Tx public key: 55f63f510d3049da599d330de2c3f8bea5f796477c88908814b93b8229d6912c
Timestamp: 1705576928 Timestamp [UCT]: 2024-01-18 11:22:08 Age [y:d:h:m:s]: 01:289:21:41:03
Block: 937963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465994 RingCT/type: yes/0
Extra: 0155f63f510d3049da599d330de2c3f8bea5f796477c88908814b93b8229d6912c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2b6aa76514a9c7927d7532f97ebfe0b6c91d33496ed71927bbb2456a88bfc5f 0.600000000000 1396027 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": 937973, "vin": [ { "gen": { "height": 937963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2b6aa76514a9c7927d7532f97ebfe0b6c91d33496ed71927bbb2456a88bfc5f" } } ], "extra": [ 1, 85, 246, 63, 81, 13, 48, 73, 218, 89, 157, 51, 13, 226, 195, 248, 190, 165, 247, 150, 71, 124, 136, 144, 136, 20, 185, 59, 130, 41, 214, 145, 44, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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