Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78bae35018b51f78c22a2f32c1653e814459847cdb3299dd9a3f5d07fe5afe01

Tx prefix hash: cbbf4056fd54f0f7a16fe919f21cb025d1582fa8ba64c308a5c1580e8e404d55
Tx public key: 0c825c43df2db335f85c1dc34fca9d262ad42f32cdd1e3b376ead15d25a4f558
Timestamp: 1766074159 Timestamp [UCT]: 2025-12-18 16:09:19 Age [y:d:h:m:s]: 00:002:18:01:39
Block: 1436397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1964 RingCT/type: yes/0
Extra: 010c825c43df2db335f85c1dc34fca9d262ad42f32cdd1e3b376ead15d25a4f5580211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ac1fd898a9b5009c7b48971728c6f8087f86da8060168f422a63aa104b28e5 0.600000000000 1925202 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": 1436407, "vin": [ { "gen": { "height": 1436397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ac1fd898a9b5009c7b48971728c6f8087f86da8060168f422a63aa104b28e5" } } ], "extra": [ 1, 12, 130, 92, 67, 223, 45, 179, 53, 248, 92, 29, 195, 79, 202, 157, 38, 42, 212, 47, 50, 205, 209, 227, 179, 118, 234, 209, 93, 37, 164, 245, 88, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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