Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 093dacfbb13b6cc4c8c1ceadb6ee0580a79cd832cd1e16893a8e55376d35b4b6

Tx prefix hash: 77d268351dd4010a3539ebc19559cb25dba0b9fb02445bfb1e7c30db76b836e6
Tx public key: a6220a12dfa0bfc4d5f843ee0ceaece0718f99a90ca0496e9df7e8209ce0ff7a
Timestamp: 1728785372 Timestamp [UCT]: 2024-10-13 02:09:32 Age [y:d:h:m:s]: 00:043:00:34:30
Block: 1130388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30724 RingCT/type: yes/0
Extra: 01a6220a12dfa0bfc4d5f843ee0ceaece0718f99a90ca0496e9df7e8209ce0ff7a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79438a32196a352b21d8c13fa3e5ab09942a004174a56020f28f125aa56e9462 0.600000000000 1613263 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": 1130398, "vin": [ { "gen": { "height": 1130388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79438a32196a352b21d8c13fa3e5ab09942a004174a56020f28f125aa56e9462" } } ], "extra": [ 1, 166, 34, 10, 18, 223, 160, 191, 196, 213, 248, 67, 238, 12, 234, 236, 224, 113, 143, 153, 169, 12, 160, 73, 110, 157, 247, 232, 32, 156, 224, 255, 122, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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