Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 749240a0e118311246b1e36959981733f41286a820e778f8d423503c9c631207

Tx prefix hash: fc8f214034bae5b6ca18d9c5a4dc2ac3efe68267b0cee75fb21e04f90c1595de
Tx public key: c0158e8cfc7e8e30faafef8b357d6d268f920ee8b1123f418ff6948627928420
Timestamp: 1736674171 Timestamp [UCT]: 2025-01-12 09:29:31 Age [y:d:h:m:s]: 00:157:20:47:16
Block: 1195650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112504 RingCT/type: yes/0
Extra: 01c0158e8cfc7e8e30faafef8b357d6d268f920ee8b1123f418ff6948627928420021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd8ce516b58aecff5facdfb06e71e4f10b69ec504c6665db871eca8e1944439 0.600000000000 1682241 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": 1195660, "vin": [ { "gen": { "height": 1195650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd8ce516b58aecff5facdfb06e71e4f10b69ec504c6665db871eca8e1944439" } } ], "extra": [ 1, 192, 21, 142, 140, 252, 126, 142, 48, 250, 175, 239, 139, 53, 125, 109, 38, 143, 146, 14, 232, 177, 18, 63, 65, 143, 246, 148, 134, 39, 146, 132, 32, 2, 17, 0, 0, 0, 2, 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