Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd36d080770516c8cedeefde6e410dd5ed689056fbcd04ed7890bc9616f2ae0

Tx prefix hash: e633875e295e5fd1153ea04577bdbcc309cece50bc6017138f6b1659f2743d58
Tx public key: c082a4bc4437f49a04c835807f2c511182e90a2591f18e97f59f71207ea64e57
Timestamp: 1749334387 Timestamp [UCT]: 2025-06-07 22:13:07 Age [y:d:h:m:s]: 00:163:19:38:09
Block: 1300201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114771 RingCT/type: yes/0
Extra: 01c082a4bc4437f49a04c835807f2c511182e90a2591f18e97f59f71207ea64e5702110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae98cb5f0a13ad8e6c3f46edabb302ce6e3c147ef5b446cb935abd0ce78f475 0.600000000000 1787750 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": 1300211, "vin": [ { "gen": { "height": 1300201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae98cb5f0a13ad8e6c3f46edabb302ce6e3c147ef5b446cb935abd0ce78f475" } } ], "extra": [ 1, 192, 130, 164, 188, 68, 55, 244, 154, 4, 200, 53, 128, 127, 44, 81, 17, 130, 233, 10, 37, 145, 241, 142, 151, 245, 159, 113, 32, 126, 166, 78, 87, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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