Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd7a31896c17be8ed128284824b75c1029c35ed57c590542b0681bea8caa16c

Tx prefix hash: 98aca9f7d766c7d4802d404456b56962f7aa2478b759a1670a9ea0ddc5e00787
Tx public key: 814b0977740a9c19f24b0b6f0f492ec069d45f81432e17b9f9bfcf36569f6907
Timestamp: 1737644102 Timestamp [UCT]: 2025-01-23 14:55:02 Age [y:d:h:m:s]: 00:145:04:51:09
Block: 1203641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103511 RingCT/type: yes/0
Extra: 01814b0977740a9c19f24b0b6f0f492ec069d45f81432e17b9f9bfcf36569f6907021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a164947a257d7d7ce3e31cd47737baf4d8eb94e4727a4932a2be82a101fd38f 0.600000000000 1690320 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": 1203651, "vin": [ { "gen": { "height": 1203641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a164947a257d7d7ce3e31cd47737baf4d8eb94e4727a4932a2be82a101fd38f" } } ], "extra": [ 1, 129, 75, 9, 119, 116, 10, 156, 25, 242, 75, 11, 111, 15, 73, 46, 192, 105, 212, 95, 129, 67, 46, 23, 185, 249, 191, 207, 54, 86, 159, 105, 7, 2, 17, 0, 0, 0, 5, 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