Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57c26424bd9bfb56068654f56063d1f707bf836618577eed92649d973d4ad00

Tx prefix hash: 876f3b5d04558a5f194a9b8fbbdc81939954802d58b2b1ff509c327b3e9326d9
Tx public key: 9f3f23e8a5ac61b61e8f4d430c04d6e9b168fcfb20af8bfa98aa730fd85b22f7
Timestamp: 1744625583 Timestamp [UCT]: 2025-04-14 10:13:03 Age [y:d:h:m:s]: 00:219:22:06:00
Block: 1261209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154905 RingCT/type: yes/0
Extra: 019f3f23e8a5ac61b61e8f4d430c04d6e9b168fcfb20af8bfa98aa730fd85b22f70211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 994d64b89406427a9c42aefa500418e1b978ace2617261e4b5f136c5c6323330 0.600000000000 1748376 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": 1261219, "vin": [ { "gen": { "height": 1261209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "994d64b89406427a9c42aefa500418e1b978ace2617261e4b5f136c5c6323330" } } ], "extra": [ 1, 159, 63, 35, 232, 165, 172, 97, 182, 30, 143, 77, 67, 12, 4, 214, 233, 177, 104, 252, 251, 32, 175, 139, 250, 152, 170, 115, 15, 216, 91, 34, 247, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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