Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ec85bc8d05ff0d17914e5389c8dd75f2e5108fcda6398eafbb1d501f660f5d

Tx prefix hash: b9c9bf7718c6cd1973b669e4b79d9edfd9f9724e7c596e4c0b10605f114f99a8
Tx public key: 9fa3b45aa04c87bc9e2c518daeb8d16ebd70c6c639e034535a8273dceadbf849
Timestamp: 1713970107 Timestamp [UCT]: 2024-04-24 14:48:27 Age [y:d:h:m:s]: 00:306:03:51:56
Block: 1007563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218834 RingCT/type: yes/0
Extra: 019fa3b45aa04c87bc9e2c518daeb8d16ebd70c6c639e034535a8273dceadbf8490211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8ac4ed8e54af40b0505ddd20d05b1020ad406dccc120755196d848da74e46b6 0.600000000000 1468947 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": 1007573, "vin": [ { "gen": { "height": 1007563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8ac4ed8e54af40b0505ddd20d05b1020ad406dccc120755196d848da74e46b6" } } ], "extra": [ 1, 159, 163, 180, 90, 160, 76, 135, 188, 158, 44, 81, 141, 174, 184, 209, 110, 189, 112, 198, 198, 57, 224, 52, 83, 90, 130, 115, 220, 234, 219, 248, 73, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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