Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daa492e330c72a4b18b012896d3a687bf07deafe93f6f5574192143b55766ad9

Tx prefix hash: 51e4b75d7724aa1f038361275191750f380988fe972d2568d11c165ec9a60c4b
Tx public key: 8bc7e377e4f1f4c4e7347420173479e06c3c494b1e5e78c9e13f2715ec51af32
Timestamp: 1699834881 Timestamp [UCT]: 2023-11-13 00:21:21 Age [y:d:h:m:s]: 01:071:00:49:36
Block: 890389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312125 RingCT/type: yes/0
Extra: 018bc7e377e4f1f4c4e7347420173479e06c3c494b1e5e78c9e13f2715ec51af3202110000000202d75dd9000000000000000000

1 output(s) for total of 0.688290258000 dcy

stealth address amount amount idx
00: c4bdd3b4b510cbab983acd006437797f7ae15a72beb9fa3fa8585d5e9d501025 0.688290258000 1346412 of 0

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": 890399, "vin": [ { "gen": { "height": 890389 } } ], "vout": [ { "amount": 688290258, "target": { "key": "c4bdd3b4b510cbab983acd006437797f7ae15a72beb9fa3fa8585d5e9d501025" } } ], "extra": [ 1, 139, 199, 227, 119, 228, 241, 244, 196, 231, 52, 116, 32, 23, 52, 121, 224, 108, 60, 73, 75, 30, 94, 120, 201, 225, 63, 39, 21, 236, 81, 175, 50, 2, 17, 0, 0, 0, 2, 2, 215, 93, 217, 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