Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a1095e55781a5dd34bd2cd12fa763121be8065aa7ef071c7d45f9f1a9cadbb5

Tx prefix hash: f9b2c43ad4117bba640d2823f3e84be7d8be2e10891d6af769853ad2695f7826
Tx public key: 32171c0c81a8d54bf6a65374844d5af8445ae5f9ec046299226a5b7db4960bf7
Timestamp: 1760363182 Timestamp [UCT]: 2025-10-13 13:46:22 Age [y:d:h:m:s]: 00:038:11:47:31
Block: 1389076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27540 RingCT/type: yes/0
Extra: 0132171c0c81a8d54bf6a65374844d5af8445ae5f9ec046299226a5b7db4960bf70211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c835d254ec30faf25f76a76990c39aa65cf1a0cb1d60790f9afb7621b8dcc99 0.600000000000 1877299 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": 1389086, "vin": [ { "gen": { "height": 1389076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c835d254ec30faf25f76a76990c39aa65cf1a0cb1d60790f9afb7621b8dcc99" } } ], "extra": [ 1, 50, 23, 28, 12, 129, 168, 213, 75, 246, 166, 83, 116, 132, 77, 90, 248, 68, 90, 229, 249, 236, 4, 98, 153, 34, 106, 91, 125, 180, 150, 11, 247, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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