Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5d4f2412034221b63639aa07e3d5e6a4b152dbb434bfbaea7c6c518132ee445

Tx prefix hash: 749f7b93afa7ff028d34ac22cb834042b848b7203d922acf41ce864cfd7e1860
Tx public key: 77024c698d0832b0f7b2e563d0fc97f410e9077d343419d54bd75bfb3e33ca9f
Timestamp: 1702061256 Timestamp [UCT]: 2023-12-08 18:47:36 Age [y:d:h:m:s]: 01:038:10:15:08
Block: 908827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288828 RingCT/type: yes/0
Extra: 0177024c698d0832b0f7b2e563d0fc97f410e9077d343419d54bd75bfb3e33ca9f02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d298709313bb3b5f8e0f746215675078916969946854444d7608e71eeb3bd2ef 0.600000000000 1365884 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": 908837, "vin": [ { "gen": { "height": 908827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d298709313bb3b5f8e0f746215675078916969946854444d7608e71eeb3bd2ef" } } ], "extra": [ 1, 119, 2, 76, 105, 141, 8, 50, 176, 247, 178, 229, 99, 208, 252, 151, 244, 16, 233, 7, 125, 52, 52, 25, 213, 75, 215, 91, 251, 62, 51, 202, 159, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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