Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1620ce8adde15490288389ab79c988d3c3217b275f8a240f054a0781e83c7846

Tx prefix hash: c3be76e0ad8af58e1f99012073c13ab71aef38b4b1aec9cf31c5105dfe95ad4c
Tx public key: 9fc72ff509ceacb0a5a7ae1df43091f781127beaff8246f23d571e77cd6f73fc
Timestamp: 1720901681 Timestamp [UCT]: 2024-07-13 20:14:41 Age [y:d:h:m:s]: 00:271:09:43:44
Block: 1065038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193903 RingCT/type: yes/0
Extra: 019fc72ff509ceacb0a5a7ae1df43091f781127beaff8246f23d571e77cd6f73fc021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e3c55eef3a606961d23f8f7d61ce51eb4d157cb3e65f399e771860e6ea36fe6 0.600000000000 1535581 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": 1065048, "vin": [ { "gen": { "height": 1065038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e3c55eef3a606961d23f8f7d61ce51eb4d157cb3e65f399e771860e6ea36fe6" } } ], "extra": [ 1, 159, 199, 47, 245, 9, 206, 172, 176, 165, 167, 174, 29, 244, 48, 145, 247, 129, 18, 123, 234, 255, 130, 70, 242, 61, 87, 30, 119, 205, 111, 115, 252, 2, 17, 0, 0, 0, 1, 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