Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74cf30a9fbbbfc2d93f4f2be00da7c3cee753b5a32467883a548f223e95adaef

Tx prefix hash: 7927423db2a73d9537e2436e776e80d5981270eb9a02f4f6a38f66460881528a
Tx public key: 87ee7dec42c376c2ab0ca6a385e140e3cc2ce6a5c19f04a48960db1134f5b689
Timestamp: 1735767186 Timestamp [UCT]: 2025-01-01 21:33:06 Age [y:d:h:m:s]: 00:097:06:59:04
Block: 1188141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69317 RingCT/type: yes/0
Extra: 0187ee7dec42c376c2ab0ca6a385e140e3cc2ce6a5c19f04a48960db1134f5b689021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5160e0dd9b9034d5a25fdf8cf8f603796bafc38edbf5e85b5520358ef165d63 0.600000000000 1674642 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": 1188151, "vin": [ { "gen": { "height": 1188141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5160e0dd9b9034d5a25fdf8cf8f603796bafc38edbf5e85b5520358ef165d63" } } ], "extra": [ 1, 135, 238, 125, 236, 66, 195, 118, 194, 171, 12, 166, 163, 133, 225, 64, 227, 204, 44, 230, 165, 193, 159, 4, 164, 137, 96, 219, 17, 52, 245, 182, 137, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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