Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca70afc46926ff2c02514a2affa8b0983ae282662d3eda584b4cdadf88f36e7b

Tx prefix hash: 1ccea283645c13e02096888b4e6a770d4b4f91e734649cf62d2fbac0d98643c6
Tx public key: b3bd658da69290a5285217641d7117a0a63a5916d955c3dfb898d2dee9700e26
Timestamp: 1731689589 Timestamp [UCT]: 2024-11-15 16:53:09 Age [y:d:h:m:s]: 01:005:00:51:16
Block: 1154368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262021 RingCT/type: yes/0
Extra: 01b3bd658da69290a5285217641d7117a0a63a5916d955c3dfb898d2dee9700e2602110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45382ce5b5f23ff7fa1d7f184d81dd1d4c619d8c5e2ea15bca57223f663b7ca7 0.600000000000 1639979 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": 1154378, "vin": [ { "gen": { "height": 1154368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45382ce5b5f23ff7fa1d7f184d81dd1d4c619d8c5e2ea15bca57223f663b7ca7" } } ], "extra": [ 1, 179, 189, 101, 141, 166, 146, 144, 165, 40, 82, 23, 100, 29, 113, 23, 160, 166, 58, 89, 22, 217, 85, 195, 223, 184, 152, 210, 222, 233, 112, 14, 38, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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