Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b44ea70e903b4c5a7daf7cf30f5c8063a2aec1b5667226135835671810681733

Tx prefix hash: 711b6372d3662def15f6d39762d291a39b247187f2ee09eac27016ad695340cb
Tx public key: f46a4f539e77c1a80e5b866a9fb0ec3124b85260ce64e7b424c799c997e2d501
Timestamp: 1736678867 Timestamp [UCT]: 2025-01-12 10:47:47 Age [y:d:h:m:s]: 00:157:12:58:02
Block: 1195693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112282 RingCT/type: yes/0
Extra: 01f46a4f539e77c1a80e5b866a9fb0ec3124b85260ce64e7b424c799c997e2d5010211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99d3cf9a0e659d1285c91e411003cd9be29e781d42f4441a8982fa4ed242b26c 0.600000000000 1682284 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": 1195703, "vin": [ { "gen": { "height": 1195693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99d3cf9a0e659d1285c91e411003cd9be29e781d42f4441a8982fa4ed242b26c" } } ], "extra": [ 1, 244, 106, 79, 83, 158, 119, 193, 168, 14, 91, 134, 106, 159, 176, 236, 49, 36, 184, 82, 96, 206, 100, 231, 180, 36, 199, 153, 201, 151, 226, 213, 1, 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