Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c48d5dace5f05f2fba53ea7bfd698f94b3f676d9620ca205c34ceb8f6719d45b

Tx prefix hash: 05072e56042b88ea97cebc3ff39e0e993f83577d42568f6433a7e6c885e982ed
Tx public key: 279e1df58831139915f6a9e19f82da60177512bda3b2d9ae42499adf1718c7d7
Timestamp: 1752279827 Timestamp [UCT]: 2025-07-12 00:23:47 Age [y:d:h:m:s]: 00:174:13:38:37
Block: 1323560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123522 RingCT/type: yes/0
Extra: 01279e1df58831139915f6a9e19f82da60177512bda3b2d9ae42499adf1718c7d70211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c236ca1ffb1a3ed649d7491ae4b45195a0e62f1cf47b47f9a734bc56c8a300ec 0.600000000000 1811299 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": 1323570, "vin": [ { "gen": { "height": 1323560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c236ca1ffb1a3ed649d7491ae4b45195a0e62f1cf47b47f9a734bc56c8a300ec" } } ], "extra": [ 1, 39, 158, 29, 245, 136, 49, 19, 153, 21, 246, 169, 225, 159, 130, 218, 96, 23, 117, 18, 189, 163, 178, 217, 174, 66, 73, 154, 223, 23, 24, 199, 215, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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