Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2982417dd3ad80d5f477b1d3298cc17cd8ff61b4cd11ad32e8b9f8a0e2f74745

Tx prefix hash: 54a2e2bbf532748e6d5cf8ae12004485d706165bdee760ea2290e46fcf210104
Tx public key: b5fdc429461942581a619a9a45787c33095b49c89eae5cae0db0461229b33dd8
Timestamp: 1712894342 Timestamp [UCT]: 2024-04-12 03:59:02 Age [y:d:h:m:s]: 01:005:01:52:24
Block: 998624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264603 RingCT/type: yes/0
Extra: 01b5fdc429461942581a619a9a45787c33095b49c89eae5cae0db0461229b33dd80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e7dcee4a94cbf9f190abfbc1be295ffd675721e13bd046deed40074107daa9 0.600000000000 1459076 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": 998634, "vin": [ { "gen": { "height": 998624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e7dcee4a94cbf9f190abfbc1be295ffd675721e13bd046deed40074107daa9" } } ], "extra": [ 1, 181, 253, 196, 41, 70, 25, 66, 88, 26, 97, 154, 154, 69, 120, 124, 51, 9, 91, 73, 200, 158, 174, 92, 174, 13, 176, 70, 18, 41, 179, 61, 216, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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