Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd916200c5be0d20768c6eaec23a7fef7aa8506b3a84c0da8ae427b5672b2e9

Tx prefix hash: 446a5433b2f164b8148c4851ec3f6c2a315b98767c6cf4f0070423dec1631fc6
Tx public key: 3512a12f30836910e1acfc8fe5b1ec5639580248708e000467312fd5cecbafab
Timestamp: 1742754176 Timestamp [UCT]: 2025-03-23 18:22:56 Age [y:d:h:m:s]: 00:047:10:49:29
Block: 1245719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33937 RingCT/type: yes/0
Extra: 013512a12f30836910e1acfc8fe5b1ec5639580248708e000467312fd5cecbafab02110000000924ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e2314720ba5e8cf5b73c5eb31b2622e6887ee96a2b4af05e6c6e0d6d8c6f46 0.600000000000 1732710 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": 1245729, "vin": [ { "gen": { "height": 1245719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e2314720ba5e8cf5b73c5eb31b2622e6887ee96a2b4af05e6c6e0d6d8c6f46" } } ], "extra": [ 1, 53, 18, 161, 47, 48, 131, 105, 16, 225, 172, 252, 143, 229, 177, 236, 86, 57, 88, 2, 72, 112, 142, 0, 4, 103, 49, 47, 213, 206, 203, 175, 171, 2, 17, 0, 0, 0, 9, 36, 255, 78, 161, 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