Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d11a6dbc5e7e1afdd79fdef21e0483089f7f6bbcaae47d3ac702e89c9725e4

Tx prefix hash: 33dd3a2c8158020e472dd84983142498d2e00dc531ccd2651e183c4e65aab5ff
Tx public key: 363a207a1096505de7871a9ee8652608bc9f52ff47690ab1f974a2b336c595cb
Timestamp: 1696958128 Timestamp [UCT]: 2023-10-10 17:15:28 Age [y:d:h:m:s]: 01:194:20:54:04
Block: 866739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400308 RingCT/type: yes/0
Extra: 01363a207a1096505de7871a9ee8652608bc9f52ff47690ab1f974a2b336c595cb02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.824392296000 dcy

stealth address amount amount idx
00: b38f20fd77512d6729c63d359d983736748f39519ef935dd6f3a21f60e6264ef 0.824392296000 1321369 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": 866749, "vin": [ { "gen": { "height": 866739 } } ], "vout": [ { "amount": 824392296, "target": { "key": "b38f20fd77512d6729c63d359d983736748f39519ef935dd6f3a21f60e6264ef" } } ], "extra": [ 1, 54, 58, 32, 122, 16, 150, 80, 93, 231, 135, 26, 158, 232, 101, 38, 8, 188, 159, 82, 255, 71, 105, 10, 177, 249, 116, 162, 179, 54, 197, 149, 203, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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