Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa74d1d30bd102bc226f5a3ec37493e3dffaa74fa26c2051b5c6d968984dde6e

Tx prefix hash: bfec42ef4bf7865e5ee65c64edb55ec38f8e599deb15f4555c95c22a20eae6ea
Tx public key: 052e6d61b9b0feefc4d6f9d4168d5de52e3f60b077a26eacee63a3527867431f
Timestamp: 1751216432 Timestamp [UCT]: 2025-06-29 17:00:32 Age [y:d:h:m:s]: 00:214:01:00:14
Block: 1315310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151032 RingCT/type: yes/0
Extra: 01052e6d61b9b0feefc4d6f9d4168d5de52e3f60b077a26eacee63a3527867431f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b691721977df36df9ea8120977e70a49796663053f2102d6ec480b89ed11ad2 0.600000000000 1802963 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": 1315320, "vin": [ { "gen": { "height": 1315310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b691721977df36df9ea8120977e70a49796663053f2102d6ec480b89ed11ad2" } } ], "extra": [ 1, 5, 46, 109, 97, 185, 176, 254, 239, 196, 214, 249, 212, 22, 141, 93, 229, 46, 63, 96, 176, 119, 162, 110, 172, 238, 99, 163, 82, 120, 103, 67, 31, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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