Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212621a81fadc31fb091ea95457807367bf4b8534d81965002c4d7c700803d67

Tx prefix hash: 1dc820690583fb7f9234edf0c6fad87737c7ce61f0e7358a3db4f96ace69cb5a
Tx public key: 1d70024211573ff990b68b15dcc8a247c8ff1c54c2ded3e228034b5015952406
Timestamp: 1685097478 Timestamp [UCT]: 2023-05-26 10:37:58 Age [y:d:h:m:s]: 01:321:03:17:55
Block: 768446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490733 RingCT/type: yes/0
Extra: 011d70024211573ff990b68b15dcc8a247c8ff1c54c2ded3e228034b501595240602110000000133af99f4000000000000000000

1 output(s) for total of 1.745097037000 dcy

stealth address amount amount idx
00: 5e8a8d4a4a5cf7e08b5bfe9d70c0438c04ee25a610d35740215f70471a84a0a5 1.745097037000 1217645 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": 768456, "vin": [ { "gen": { "height": 768446 } } ], "vout": [ { "amount": 1745097037, "target": { "key": "5e8a8d4a4a5cf7e08b5bfe9d70c0438c04ee25a610d35740215f70471a84a0a5" } } ], "extra": [ 1, 29, 112, 2, 66, 17, 87, 63, 249, 144, 182, 139, 21, 220, 200, 162, 71, 200, 255, 28, 84, 194, 222, 211, 226, 40, 3, 75, 80, 21, 149, 36, 6, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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