Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7088d4cd4b6064e90d8135aea6c8522ebfa112116c7168dc5b0fb85c7c381b4a

Tx prefix hash: 0d9dd9fef5fbb7263cd9047b0b590504dced8988bdf11ffd79250594c7ac4504
Tx public key: 2f53ee129d1f5011d2bb6c0ef4ed662938837d4c303b2a265e55c7dbde5dfbf9
Timestamp: 1713568276 Timestamp [UCT]: 2024-04-19 23:11:16 Age [y:d:h:m:s]: 00:355:07:35:53
Block: 1004214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254035 RingCT/type: yes/0
Extra: 012f53ee129d1f5011d2bb6c0ef4ed662938837d4c303b2a265e55c7dbde5dfbf90211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69011f57f261053a8473677ba1ca70dfe26a16345da947152c3e1c9f331f6fee 0.600000000000 1464782 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": 1004224, "vin": [ { "gen": { "height": 1004214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69011f57f261053a8473677ba1ca70dfe26a16345da947152c3e1c9f331f6fee" } } ], "extra": [ 1, 47, 83, 238, 18, 157, 31, 80, 17, 210, 187, 108, 14, 244, 237, 102, 41, 56, 131, 125, 76, 48, 59, 42, 38, 94, 85, 199, 219, 222, 93, 251, 249, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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