Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0fa546c2da5524c9bfd25316f82dfdb1fa4b7e14300cc217d811e0fc4a6046d

Tx prefix hash: 19534019aaf5401f1b92bca91d86526b8d6d5c00a20fb7cc1b2c1869ba38fcf1
Tx public key: 3088cb31773ef0bee8072b50578f0dccec35c1fb6ad9b47aedfbeba79249aa50
Timestamp: 1709517140 Timestamp [UCT]: 2024-03-04 01:52:20 Age [y:d:h:m:s]: 01:010:21:31:20
Block: 970656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268788 RingCT/type: yes/0
Extra: 013088cb31773ef0bee8072b50578f0dccec35c1fb6ad9b47aedfbeba79249aa5002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c43e15e5df1135a642a6287440b620498363801732b7b9ad9baba9f2505184d 0.600000000000 1430515 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": 970666, "vin": [ { "gen": { "height": 970656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c43e15e5df1135a642a6287440b620498363801732b7b9ad9baba9f2505184d" } } ], "extra": [ 1, 48, 136, 203, 49, 119, 62, 240, 190, 232, 7, 43, 80, 87, 143, 13, 204, 236, 53, 193, 251, 106, 217, 180, 122, 237, 251, 235, 167, 146, 73, 170, 80, 2, 17, 0, 0, 0, 3, 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