Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa11cf9795288080312602a29e8c8367c4e4fe7f14e3fbeecb5069a9636b9faa

Tx prefix hash: 0e75824b398d90fcd7a3c1d03f768fefb45e00a7e8543041505c028a0bee447a
Tx public key: b43e7813661ddbb7ca84c560a7480bf6ea25893e778545fb0d32dbc0586f8404
Timestamp: 1737583218 Timestamp [UCT]: 2025-01-22 22:00:18 Age [y:d:h:m:s]: 00:051:03:56:59
Block: 1203130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36399 RingCT/type: yes/0
Extra: 01b43e7813661ddbb7ca84c560a7480bf6ea25893e778545fb0d32dbc0586f84040211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46d408ed0b08c45ddb3ff0ec43f3c139adcbe12f9e0e8b87b9e3e21ce1f94aec 0.600000000000 1689803 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": 1203140, "vin": [ { "gen": { "height": 1203130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46d408ed0b08c45ddb3ff0ec43f3c139adcbe12f9e0e8b87b9e3e21ce1f94aec" } } ], "extra": [ 1, 180, 62, 120, 19, 102, 29, 219, 183, 202, 132, 197, 96, 167, 72, 11, 246, 234, 37, 137, 62, 119, 133, 69, 251, 13, 50, 219, 192, 88, 111, 132, 4, 2, 17, 0, 0, 0, 3, 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