Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832b1045f66ac5637c86eec96de979f0fb09a7d1cfc8973743cc0a6f5e7ba479

Tx prefix hash: 0c870b3023afb69490a1c79cd6efc4b9a4f7dd89f1acda3671e5729ef6caed92
Tx public key: a3b4d09b78b0f0fd9e7c9de58165d32525b028c5e64401c1a50420f9e5ba6322
Timestamp: 1635900947 Timestamp [UCT]: 2021-11-03 00:55:47 Age [y:d:h:m:s]: 03:025:00:42:20
Block: 366122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 796384 RingCT/type: yes/0
Extra: 01a3b4d09b78b0f0fd9e7c9de58165d32525b028c5e64401c1a50420f9e5ba632202110000003df56b629f000000000000000000

1 output(s) for total of 37.575576046000 dcy

stealth address amount amount idx
00: 1d5ce6eb2913197dd0a14eccdea8a39c8856a108b4537d40f4e534446e40459f 37.575576046000 743312 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": 366132, "vin": [ { "gen": { "height": 366122 } } ], "vout": [ { "amount": 37575576046, "target": { "key": "1d5ce6eb2913197dd0a14eccdea8a39c8856a108b4537d40f4e534446e40459f" } } ], "extra": [ 1, 163, 180, 208, 155, 120, 176, 240, 253, 158, 124, 157, 229, 129, 101, 211, 37, 37, 176, 40, 197, 230, 68, 1, 193, 165, 4, 32, 249, 229, 186, 99, 34, 2, 17, 0, 0, 0, 61, 245, 107, 98, 159, 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