Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c98fe48b1137e0a8051201fadc16d267e68dfc8cc7d6fca4a49faa00f7aa78b

Tx prefix hash: b72cfcce6dd659f050fe7ca35c67c9d415a2a619dc93ffb7d3c38ded9eadf8c2
Tx public key: 32a5fd4db83cf186368054d59e96a1e834ee94e9885ceecd6cfe76cd9b8a5211
Timestamp: 1737652843 Timestamp [UCT]: 2025-01-23 17:20:43 Age [y:d:h:m:s]: 00:328:02:28:15
Block: 1203712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232070 RingCT/type: yes/0
Extra: 0132a5fd4db83cf186368054d59e96a1e834ee94e9885ceecd6cfe76cd9b8a52110211000000141f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f92548db0d40b394c7f9290428be9f9355f134c47d53312c8a67ce3da4975810 0.600000000000 1690391 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": 1203722, "vin": [ { "gen": { "height": 1203712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f92548db0d40b394c7f9290428be9f9355f134c47d53312c8a67ce3da4975810" } } ], "extra": [ 1, 50, 165, 253, 77, 184, 60, 241, 134, 54, 128, 84, 213, 158, 150, 161, 232, 52, 238, 148, 233, 136, 92, 238, 205, 108, 254, 118, 205, 155, 138, 82, 17, 2, 17, 0, 0, 0, 20, 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