Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d754afd63a4cbec388748f5ccda75c68eb53cd0971d07096fd5590402e55a300

Tx prefix hash: 0eaf4491ab9a0bf2f02df6ba962f2cf513ba0987344e2eda73da1f8dced0eaf6
Tx public key: ef37df41ed80fd637323c6a8b6e96c98045d5a957f5c616213dfe47fb6bd3f23
Timestamp: 1749307016 Timestamp [UCT]: 2025-06-07 14:36:56 Age [y:d:h:m:s]: 00:159:18:15:30
Block: 1299978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111862 RingCT/type: yes/0
Extra: 01ef37df41ed80fd637323c6a8b6e96c98045d5a957f5c616213dfe47fb6bd3f23021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1069498ca6396c1ae3ac2dfff8bbe4241cb3e89b70ed1aef98792aca737416f2 0.600000000000 1787521 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": 1299988, "vin": [ { "gen": { "height": 1299978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1069498ca6396c1ae3ac2dfff8bbe4241cb3e89b70ed1aef98792aca737416f2" } } ], "extra": [ 1, 239, 55, 223, 65, 237, 128, 253, 99, 115, 35, 198, 168, 182, 233, 108, 152, 4, 93, 90, 149, 127, 92, 97, 98, 19, 223, 228, 127, 182, 189, 63, 35, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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