Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe24a1d098c97a32192a8d0250f1e90c518dace0a2e36e8829faf955664c1ac7

Tx prefix hash: 83f8e43ab136a2fb42c9d6bb8775ff6ab39f36efc980d114a48d3ac3e41290d3
Tx public key: 7df990f094bfe6bd2650453f678b89537c94b39df706ff24f42dc42ddf14f897
Timestamp: 1733653884 Timestamp [UCT]: 2024-12-08 10:31:24 Age [y:d:h:m:s]: 00:155:18:27:03
Block: 1170660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111136 RingCT/type: yes/0
Extra: 017df990f094bfe6bd2650453f678b89537c94b39df706ff24f42dc42ddf14f897021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b343b337f3e320e7f0338dc9ef055a72139fe326f937c2dc671c65dc080e51c1 0.600000000000 1656391 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": 1170670, "vin": [ { "gen": { "height": 1170660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b343b337f3e320e7f0338dc9ef055a72139fe326f937c2dc671c65dc080e51c1" } } ], "extra": [ 1, 125, 249, 144, 240, 148, 191, 230, 189, 38, 80, 69, 63, 103, 139, 137, 83, 124, 148, 179, 157, 247, 6, 255, 36, 244, 45, 196, 45, 223, 20, 248, 151, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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