Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99b0104a68129bed052daf4790eaa74e5e96f0557a268e334a5d47b782cbf711

Tx prefix hash: 75f67763dc60e902b549fd09fb427f1923a8e45bbfe2f97e09301196bc762ec0
Tx public key: f08ec2128f2d25250aae85d9419de47881c5a7fe0ce92f85a60ab12dc55ef3eb
Timestamp: 1752032319 Timestamp [UCT]: 2025-07-09 03:38:39 Age [y:d:h:m:s]: 00:135:00:49:25
Block: 1321707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94993 RingCT/type: yes/0
Extra: 01f08ec2128f2d25250aae85d9419de47881c5a7fe0ce92f85a60ab12dc55ef3eb021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7223c1bb7db9133685b405a47bc9ce11248b7e014a34b9446cb5c453c5ceb8f1 0.600000000000 1809416 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": 1321717, "vin": [ { "gen": { "height": 1321707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7223c1bb7db9133685b405a47bc9ce11248b7e014a34b9446cb5c453c5ceb8f1" } } ], "extra": [ 1, 240, 142, 194, 18, 143, 45, 37, 37, 10, 174, 133, 217, 65, 157, 228, 120, 129, 197, 167, 254, 12, 233, 47, 133, 166, 10, 177, 45, 197, 94, 243, 235, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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