Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ed24d5351d59e2aaeaaf4105747e37d4ab86c14429800d7df3c11b996aa08c

Tx prefix hash: 82146f9110bdbb9fb102a81e4dacb399db3e1168b0cc4ae0fab5fe8b7ca5f15f
Tx public key: b06d0e75af9177af9b40465b0bf1ec01fcd4a12fd640dc0ee518bdebae4edd8b
Timestamp: 1675252479 Timestamp [UCT]: 2023-02-01 11:54:39 Age [y:d:h:m:s]: 02:064:18:41:34
Block: 687459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567920 RingCT/type: yes/0
Extra: 01b06d0e75af9177af9b40465b0bf1ec01fcd4a12fd640dc0ee518bdebae4edd8b0211000000045029cbac000000000000000000

1 output(s) for total of 3.237150470000 dcy

stealth address amount amount idx
00: ff5665e2f111f5d3f3578b108a9f98f316f57e0b4a397de0c7e3aae4d9623b63 3.237150470000 1130024 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": 687469, "vin": [ { "gen": { "height": 687459 } } ], "vout": [ { "amount": 3237150470, "target": { "key": "ff5665e2f111f5d3f3578b108a9f98f316f57e0b4a397de0c7e3aae4d9623b63" } } ], "extra": [ 1, 176, 109, 14, 117, 175, 145, 119, 175, 155, 64, 70, 91, 11, 241, 236, 1, 252, 212, 161, 47, 214, 64, 220, 14, 229, 24, 189, 235, 174, 78, 221, 139, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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