Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28fe4762f2ab2fdea75e2bccd529c7ef7c7ca13a2d266cb02a4fe698cbee8f53

Tx prefix hash: 942a8a42766cdc5d8a5a629cfd74722e7f43b56eb946dca70c6aa7264fe71837
Tx public key: 73cc59199ca15ada74865d6de3a2e03791b04a47def5f8660cead19af4335a73
Timestamp: 1735273492 Timestamp [UCT]: 2024-12-27 04:24:52 Age [y:d:h:m:s]: 00:082:17:13:31
Block: 1184060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58922 RingCT/type: yes/0
Extra: 0173cc59199ca15ada74865d6de3a2e03791b04a47def5f8660cead19af4335a730211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3025e3e24011fdbcf4d3a3ed5e25b8540eb7e83cf43645fab6b2e8bdf2ca13a 0.600000000000 1670513 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": 1184070, "vin": [ { "gen": { "height": 1184060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3025e3e24011fdbcf4d3a3ed5e25b8540eb7e83cf43645fab6b2e8bdf2ca13a" } } ], "extra": [ 1, 115, 204, 89, 25, 156, 161, 90, 218, 116, 134, 93, 109, 227, 162, 224, 55, 145, 176, 74, 71, 222, 245, 248, 102, 12, 234, 209, 154, 244, 51, 90, 115, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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