Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c72936535cc3dcf4d1dba38a8a98a4a7e12646c7d3ef3eb08c5cae494598870

Tx prefix hash: 9f73ccd21f46120a7f7eb9f15ada05bcacb0d88e1b89700665bb703dc8d6caec
Tx public key: 24a3cb74aece10ea7542a9c484b4c076b7c60ab727344109c60913d1228f0e32
Timestamp: 1722836173 Timestamp [UCT]: 2024-08-05 05:36:13 Age [y:d:h:m:s]: 00:244:04:01:24
Block: 1081060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174408 RingCT/type: yes/0
Extra: 0124a3cb74aece10ea7542a9c484b4c076b7c60ab727344109c60913d1228f0e32021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a50136d912ef8579e48e129c4d93353be47b32a2a7e2a14992702eea3a6911f 0.600000000000 1554661 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": 1081070, "vin": [ { "gen": { "height": 1081060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a50136d912ef8579e48e129c4d93353be47b32a2a7e2a14992702eea3a6911f" } } ], "extra": [ 1, 36, 163, 203, 116, 174, 206, 16, 234, 117, 66, 169, 196, 132, 180, 192, 118, 183, 198, 10, 183, 39, 52, 65, 9, 198, 9, 19, 209, 34, 143, 14, 50, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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