Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32853e73855fd6e1f726bf64365bc75944e831c614337176686ce214d472e0f

Tx prefix hash: 8483e5cbeef2add2529849c1f5f92f8085df2ddf9b13966ef289251b4feb913f
Tx public key: e9fc3caaf0f5a4e42ffa32b7d8c96ecae22e6dbfe669bc9a20e0df2af67c5e75
Timestamp: 1727359524 Timestamp [UCT]: 2024-09-26 14:05:24 Age [y:d:h:m:s]: 00:196:08:44:29
Block: 1118574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140145 RingCT/type: yes/0
Extra: 01e9fc3caaf0f5a4e42ffa32b7d8c96ecae22e6dbfe669bc9a20e0df2af67c5e7502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41dcc825e067bf9618e560b6be06abd12b90473bc7e0249c1ef1e78aca4991fe 0.600000000000 1599811 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": 1118584, "vin": [ { "gen": { "height": 1118574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41dcc825e067bf9618e560b6be06abd12b90473bc7e0249c1ef1e78aca4991fe" } } ], "extra": [ 1, 233, 252, 60, 170, 240, 245, 164, 228, 47, 250, 50, 183, 216, 201, 110, 202, 226, 46, 109, 191, 230, 105, 188, 154, 32, 224, 223, 42, 246, 124, 94, 117, 2, 17, 0, 0, 0, 3, 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