Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48bc2f8c1734c58ef245d4cb6944edc5c3c1c9814060d01c23a9f5caaa09b67

Tx prefix hash: c932d616cd55b48d28ffa6a384bddcc2d06966fd425e3a200cb88c692e4d2567
Tx public key: 7b9144f1fac038150607074a0e805be7f96fdcd10adbd648eb0f8abdb0dc4bc8
Timestamp: 1584634492 Timestamp [UCT]: 2020-03-19 16:14:52 Age [y:d:h:m:s]: 04:327:05:37:11
Block: 85403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129670 RingCT/type: yes/0
Extra: 017b9144f1fac038150607074a0e805be7f96fdcd10adbd648eb0f8abdb0dc4bc8021100000196e1f32f7d000000000000000000

1 output(s) for total of 319.908066188000 dcy

stealth address amount amount idx
00: 9be721c293af2efadb465ae3da3b6bf4e439885e7d18ecc4c78251b4358e0d23 319.908066188000 154421 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": 85413, "vin": [ { "gen": { "height": 85403 } } ], "vout": [ { "amount": 319908066188, "target": { "key": "9be721c293af2efadb465ae3da3b6bf4e439885e7d18ecc4c78251b4358e0d23" } } ], "extra": [ 1, 123, 145, 68, 241, 250, 192, 56, 21, 6, 7, 7, 74, 14, 128, 91, 231, 249, 111, 220, 209, 10, 219, 214, 72, 235, 15, 138, 189, 176, 220, 75, 200, 2, 17, 0, 0, 1, 150, 225, 243, 47, 125, 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