Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ec20b36f6bdd669f85bfe2541a7ac71c3542aaa9c73f1f38dec9ecd693ef29

Tx prefix hash: 84596d614944c50d9b6526c67e5262649311fdec6393304df4c7c1075da249d3
Tx public key: ed1086ad585a9c24b3e3e9b737079c7900e5f714ffc250d1187c9d0b429f3f91
Timestamp: 1720129417 Timestamp [UCT]: 2024-07-04 21:43:37 Age [y:d:h:m:s]: 00:269:20:46:48
Block: 1058620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192822 RingCT/type: yes/0
Extra: 01ed1086ad585a9c24b3e3e9b737079c7900e5f714ffc250d1187c9d0b429f3f910211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d4556ab323bc56d3ff740cbf2427ad141ffc121b7619fa4247fe223c22782fd 0.600000000000 1529077 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": 1058630, "vin": [ { "gen": { "height": 1058620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d4556ab323bc56d3ff740cbf2427ad141ffc121b7619fa4247fe223c22782fd" } } ], "extra": [ 1, 237, 16, 134, 173, 88, 90, 156, 36, 179, 227, 233, 183, 55, 7, 156, 121, 0, 229, 247, 20, 255, 194, 80, 209, 24, 124, 157, 11, 66, 159, 63, 145, 2, 17, 0, 0, 0, 1, 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