Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22623a67f661ae396c2493e0cd93c816298ae7ce01d14fb77bec06e0cffda483

Tx prefix hash: 393ecb6a8048d3e4090dc6031a85000daf2b1a12d6878dd3afdf775fc2bd3667
Tx public key: dd745ca641e875a938a8a56d520674b333a4eb4b255f10c77811440ade45dbe9
Timestamp: 1696524384 Timestamp [UCT]: 2023-10-05 16:46:24 Age [y:d:h:m:s]: 01:258:00:04:16
Block: 863127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445366 RingCT/type: yes/0
Extra: 01dd745ca641e875a938a8a56d520674b333a4eb4b255f10c77811440ade45dbe9021100000008faf35c9c000000000000000000

1 output(s) for total of 0.847426392000 dcy

stealth address amount amount idx
00: d38ebd00ab1b1858bd40f1965f3b34f084c9d2a82cbf2e0c0099b92c516d0d3c 0.847426392000 1317575 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": 863137, "vin": [ { "gen": { "height": 863127 } } ], "vout": [ { "amount": 847426392, "target": { "key": "d38ebd00ab1b1858bd40f1965f3b34f084c9d2a82cbf2e0c0099b92c516d0d3c" } } ], "extra": [ 1, 221, 116, 92, 166, 65, 232, 117, 169, 56, 168, 165, 109, 82, 6, 116, 179, 51, 164, 235, 75, 37, 95, 16, 199, 120, 17, 68, 10, 222, 69, 219, 233, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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