Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae7736e6528a29af08c8c4f2f86d8e0931ab4e0dbb9b991fd1b4ffddc06890c5

Tx prefix hash: b14e973e03f6ea0de5174ce61c7d2505733ab0463b9a84876ffb6b3849017932
Tx public key: 2f54df0d5b0d37434b62943d013b8b9abed77b7366593a38379c7fc1e50982b6
Timestamp: 1736876293 Timestamp [UCT]: 2025-01-14 17:38:13 Age [y:d:h:m:s]: 00:156:02:27:53
Block: 1197322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111259 RingCT/type: yes/0
Extra: 012f54df0d5b0d37434b62943d013b8b9abed77b7366593a38379c7fc1e50982b60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd2ddb1f467f52b836b8e14364bcbec5f0d70f000e7a9859ad8f16e2aa17a11d 0.600000000000 1683929 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": 1197332, "vin": [ { "gen": { "height": 1197322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd2ddb1f467f52b836b8e14364bcbec5f0d70f000e7a9859ad8f16e2aa17a11d" } } ], "extra": [ 1, 47, 84, 223, 13, 91, 13, 55, 67, 75, 98, 148, 61, 1, 59, 139, 154, 190, 215, 123, 115, 102, 89, 58, 56, 55, 156, 127, 193, 229, 9, 130, 182, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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