Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7974c29419e750bfa14742933c656292a84403a6159815b2c9a3557c1522c24

Tx prefix hash: 12067d55592bff506b8f67ed046b9c5d8ec552e5414a1f25dc51485e9c161104
Tx public key: b1fb9058bb749c88359150aa011a39fd6cfa317dbcb341b484faf61babc668b8
Timestamp: 1639136029 Timestamp [UCT]: 2021-12-10 11:33:49 Age [y:d:h:m:s]: 02:355:11:57:24
Block: 392467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772128 RingCT/type: yes/0
Extra: 01b1fb9058bb749c88359150aa011a39fd6cfa317dbcb341b484faf61babc668b8021100000002b494d89c000000000000000000

1 output(s) for total of 30.732243861000 dcy

stealth address amount amount idx
00: 595bbdb26e29e797a1b8c9996b0266f50d67d5efa6102c2e01bc8d380f9edbca 30.732243861000 789346 of 0

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": 392477, "vin": [ { "gen": { "height": 392467 } } ], "vout": [ { "amount": 30732243861, "target": { "key": "595bbdb26e29e797a1b8c9996b0266f50d67d5efa6102c2e01bc8d380f9edbca" } } ], "extra": [ 1, 177, 251, 144, 88, 187, 116, 156, 136, 53, 145, 80, 170, 1, 26, 57, 253, 108, 250, 49, 125, 188, 179, 65, 180, 132, 250, 246, 27, 171, 198, 104, 184, 2, 17, 0, 0, 0, 2, 180, 148, 216, 156, 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