Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb48c389cff48ddb0d2251ad7164132e77f2e43e6236967e9d1f27c9a5abbc83

Tx prefix hash: 8e9f1692b72a698b9bfd458eb8deabc8fc11a1ccd44e50396603dc724826df31
Tx public key: 5f43eef983f7e2f882d3da30e7ef1a1308ee4466133b82fe8aabfb891d9ef1e4
Timestamp: 1680101613 Timestamp [UCT]: 2023-03-29 14:53:33 Age [y:d:h:m:s]: 01:296:15:18:19
Block: 727680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472838 RingCT/type: yes/0
Extra: 015f43eef983f7e2f882d3da30e7ef1a1308ee4466133b82fe8aabfb891d9ef1e402110000000333af99f4000000000000000000

1 output(s) for total of 2.381739841000 dcy

stealth address amount amount idx
00: c410cb72d2162426a157478b19154321f6223b65ea2df5eb2e6e0b29f3ae55e1 2.381739841000 1173005 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": 727690, "vin": [ { "gen": { "height": 727680 } } ], "vout": [ { "amount": 2381739841, "target": { "key": "c410cb72d2162426a157478b19154321f6223b65ea2df5eb2e6e0b29f3ae55e1" } } ], "extra": [ 1, 95, 67, 238, 249, 131, 247, 226, 248, 130, 211, 218, 48, 231, 239, 26, 19, 8, 238, 68, 102, 19, 59, 130, 254, 138, 171, 251, 137, 29, 158, 241, 228, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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