Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e493fc28a576dd0586fb433ce64658e6c714f5062ca46347f4c41ee8b8368253

Tx prefix hash: b35c0d976db8094bdde6d5e7c53d9444adf665773fe748ea515c2e257319bd6f
Tx public key: f2a676567562c067133d9693c490680f1ae12dd4ea5c1364d10d312c47b82343
Timestamp: 1728838851 Timestamp [UCT]: 2024-10-13 17:00:51 Age [y:d:h:m:s]: 00:220:13:10:30
Block: 1130833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157445 RingCT/type: yes/0
Extra: 01f2a676567562c067133d9693c490680f1ae12dd4ea5c1364d10d312c47b8234302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db68fa3e8b45087571a6ef1b0e09d04affdfa6b388e5ad90b8710274ae983190 0.600000000000 1613714 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": 1130843, "vin": [ { "gen": { "height": 1130833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db68fa3e8b45087571a6ef1b0e09d04affdfa6b388e5ad90b8710274ae983190" } } ], "extra": [ 1, 242, 166, 118, 86, 117, 98, 192, 103, 19, 61, 150, 147, 196, 144, 104, 15, 26, 225, 45, 212, 234, 92, 19, 100, 209, 13, 49, 44, 71, 184, 35, 67, 2, 17, 0, 0, 0, 5, 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