Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5a5f1e402f7f19db866c2aa0a93916ad7e6ccc3b4c8f719c4f0434445902e3f

Tx prefix hash: 6ba7d25a273545bd656f21b69cc13ee692c4476bb9be4b841475b0c18b03b44f
Tx public key: dac18ee479922de512b54ece6aef5718abd105922b8cfa41f6e5c72cf144dd7f
Timestamp: 1706587242 Timestamp [UCT]: 2024-01-30 04:00:42 Age [y:d:h:m:s]: 01:138:23:51:25
Block: 946335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360357 RingCT/type: yes/0
Extra: 01dac18ee479922de512b54ece6aef5718abd105922b8cfa41f6e5c72cf144dd7f0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6a4a9e15ff701b133dad9f335f181fc839c15747bd131f0a7910894e4d48f1f 0.600000000000 1404667 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": 946345, "vin": [ { "gen": { "height": 946335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a4a9e15ff701b133dad9f335f181fc839c15747bd131f0a7910894e4d48f1f" } } ], "extra": [ 1, 218, 193, 142, 228, 121, 146, 45, 229, 18, 181, 78, 206, 106, 239, 87, 24, 171, 209, 5, 146, 43, 140, 250, 65, 246, 229, 199, 44, 241, 68, 221, 127, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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