Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f57f351bb6ee0013fa3456d67e6797b56a5c8a1d65cb4764cd8e950217634a5

Tx prefix hash: 31cab59eb04569a495e5e378c990083a89a4efdf0c5de3a49af43f0103005e7b
Tx public key: 01b444798238b2578abfe11f9f9da31c4637e966a65171cf4c06b1192463d720
Timestamp: 1696698666 Timestamp [UCT]: 2023-10-07 17:11:06 Age [y:d:h:m:s]: 01:181:15:51:01
Block: 864577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390873 RingCT/type: yes/0
Extra: 0101b444798238b2578abfe11f9f9da31c4637e966a65171cf4c06b1192463d72002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.838103263000 dcy

stealth address amount amount idx
00: d186ce29e2d8cf5a9b2778aac762c868d9d09dcef0b1556bca2cb5e9c706ebf7 0.838103263000 1319097 of 0

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": 864587, "vin": [ { "gen": { "height": 864577 } } ], "vout": [ { "amount": 838103263, "target": { "key": "d186ce29e2d8cf5a9b2778aac762c868d9d09dcef0b1556bca2cb5e9c706ebf7" } } ], "extra": [ 1, 1, 180, 68, 121, 130, 56, 178, 87, 138, 191, 225, 31, 159, 157, 163, 28, 70, 55, 233, 102, 166, 81, 113, 207, 76, 6, 177, 25, 36, 99, 215, 32, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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