Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14f2fec70e573223d0e5f577c95a536ce8164bbff17e1625e77d10d2c4b88dc

Tx prefix hash: 8fa76df8313972554c2c82e48f9937baade1c7ae4c3b48fd944bc81b2f109527
Tx public key: 5cef7a539deedbc368b01c96a873976da605d1cf5eb6b2b827b377f385ec3c15
Timestamp: 1751095170 Timestamp [UCT]: 2025-06-28 07:19:30 Age [y:d:h:m:s]: 00:145:19:50:23
Block: 1314356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102306 RingCT/type: yes/0
Extra: 015cef7a539deedbc368b01c96a873976da605d1cf5eb6b2b827b377f385ec3c1502110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e7f3b4efd6c48f84e4dd5e9f3e77516a78dde50ab8b422bcdca02727e18f93d 0.600000000000 1802003 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": 1314366, "vin": [ { "gen": { "height": 1314356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e7f3b4efd6c48f84e4dd5e9f3e77516a78dde50ab8b422bcdca02727e18f93d" } } ], "extra": [ 1, 92, 239, 122, 83, 157, 238, 219, 195, 104, 176, 28, 150, 168, 115, 151, 109, 166, 5, 209, 207, 94, 182, 178, 184, 39, 179, 119, 243, 133, 236, 60, 21, 2, 17, 0, 0, 0, 2, 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