Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07c2a0815e0e1a77a33f314a12174705be86c10d8ad5903067be41e745f57551

Tx prefix hash: 211c944ff9b3b3095f7acba6d3ac3a2b11aa332e1ac0bf7651e4f8ce27e1590c
Tx public key: d89dfdeaa5757840675f5d7e38a591aad5d383e7a1974a28a60227789a2f804f
Timestamp: 1645330009 Timestamp [UCT]: 2022-02-20 04:06:49 Age [y:d:h:m:s]: 03:265:03:30:16
Block: 442375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 967269 RingCT/type: yes/0
Extra: 01d89dfdeaa5757840675f5d7e38a591aad5d383e7a1974a28a60227789a2f804f0211000000014a0f5013000000000000000000

1 output(s) for total of 21.000434304000 dcy

stealth address amount amount idx
00: 574527688d6eac0935d32590b5e44cf1cd757eefbbacedd9ee2216de1b5efbe8 21.000434304000 855146 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": 442385, "vin": [ { "gen": { "height": 442375 } } ], "vout": [ { "amount": 21000434304, "target": { "key": "574527688d6eac0935d32590b5e44cf1cd757eefbbacedd9ee2216de1b5efbe8" } } ], "extra": [ 1, 216, 157, 253, 234, 165, 117, 120, 64, 103, 95, 93, 126, 56, 165, 145, 170, 213, 211, 131, 231, 161, 151, 74, 40, 166, 2, 39, 120, 154, 47, 128, 79, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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