Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b720b3c61138c2796c86dac08eb588fed3d1de898ceb9ec40daa2423b377e6a

Tx prefix hash: 7102a46f566724e5c58d439afd6b015889455533258955a9256f602012706e5f
Tx public key: 3f04d7b32ed4f09a9c0f5a0f4a2a9aa898c3297722848bc2f31e32c16b1cb1e8
Timestamp: 1707335054 Timestamp [UCT]: 2024-02-07 19:44:14 Age [y:d:h:m:s]: 01:018:14:27:36
Block: 952553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274314 RingCT/type: yes/0
Extra: 013f04d7b32ed4f09a9c0f5a0f4a2a9aa898c3297722848bc2f31e32c16b1cb1e802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12b2c1a7c5a055ba5d9fb94294aba2887e11dfa7e07fe4cd7e1e4a2710a75f1a 0.600000000000 1411595 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": 952563, "vin": [ { "gen": { "height": 952553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12b2c1a7c5a055ba5d9fb94294aba2887e11dfa7e07fe4cd7e1e4a2710a75f1a" } } ], "extra": [ 1, 63, 4, 215, 179, 46, 212, 240, 154, 156, 15, 90, 15, 74, 42, 154, 168, 152, 195, 41, 119, 34, 132, 139, 194, 243, 30, 50, 193, 107, 28, 177, 232, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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