Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f69c7248ca8ee96e96242259dea9572efebf797057ad178e8c2f12e6967a062f

Tx prefix hash: 06d8c37642f0c8e19bd16eec0a5ffe9215f3b4839d55dd0dcf9e87b05fec9ab0
Tx public key: 53c0804662e166d636c69d7eafbbc81714fde526ff41bd003e6503af158e50b0
Timestamp: 1727088674 Timestamp [UCT]: 2024-09-23 10:51:14 Age [y:d:h:m:s]: 00:231:08:40:31
Block: 1116323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165193 RingCT/type: yes/0
Extra: 0153c0804662e166d636c69d7eafbbc81714fde526ff41bd003e6503af158e50b0021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e775f188c9e8b710db47b3a875c8e03bce66f69e3e96f1e2b68314e9f4a069f3 0.600000000000 1596766 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": 1116333, "vin": [ { "gen": { "height": 1116323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e775f188c9e8b710db47b3a875c8e03bce66f69e3e96f1e2b68314e9f4a069f3" } } ], "extra": [ 1, 83, 192, 128, 70, 98, 225, 102, 214, 54, 198, 157, 126, 175, 187, 200, 23, 20, 253, 229, 38, 255, 65, 189, 0, 62, 101, 3, 175, 21, 142, 80, 176, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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