Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d2e3361be190eaaaf6503f6b8030bcc05775774f95ae680a2d5f3d4e1c277c6

Tx prefix hash: 51f619585e26539f5655ed9260bc95af25c5b04935f5a8f5a164f20f01f012be
Tx public key: 3c055a121c287ccee9ad64ba5e72d7f501018f25e81dcf9b7381d944ee369456
Timestamp: 1749136082 Timestamp [UCT]: 2025-06-05 15:08:02 Age [y:d:h:m:s]: 00:164:01:29:08
Block: 1298571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114924 RingCT/type: yes/0
Extra: 013c055a121c287ccee9ad64ba5e72d7f501018f25e81dcf9b7381d944ee36945602110000000a43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57aa662a5a792d3a96bca3becd0d9e1d8a6ae84c9b3153650ceee61c4a01ab76 0.600000000000 1786100 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": 1298581, "vin": [ { "gen": { "height": 1298571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57aa662a5a792d3a96bca3becd0d9e1d8a6ae84c9b3153650ceee61c4a01ab76" } } ], "extra": [ 1, 60, 5, 90, 18, 28, 40, 124, 206, 233, 173, 100, 186, 94, 114, 215, 245, 1, 1, 143, 37, 232, 29, 207, 155, 115, 129, 217, 68, 238, 54, 148, 86, 2, 17, 0, 0, 0, 10, 67, 132, 109, 102, 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