Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad2048decb82ac34005d2612d084314a4d7135c5ffbafe105814a3adca679b6

Tx prefix hash: 672d76d1f0758b1d0f8006c1d684ef7d733a8cd0e8d59d50c9619d4f5af8f992
Tx public key: f7c5f04276a64a6aa2571c3479146b3df64af90dfbd2b32d44f2a67d5265b279
Timestamp: 1582988347 Timestamp [UCT]: 2020-02-29 14:59:07 Age [y:d:h:m:s]: 04:271:09:56:09
Block: 74211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087557 RingCT/type: yes/0
Extra: 01f7c5f04276a64a6aa2571c3479146b3df64af90dfbd2b32d44f2a67d5265b2790211000000ac026b59f3000000000000000000

1 output(s) for total of 348.424711391000 dcy

stealth address amount amount idx
00: 28bb06343caf032d07af2b7dca728f6cdc57b2c949f2ec95b8d6c0bdffddd869 348.424711391000 137202 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": 74221, "vin": [ { "gen": { "height": 74211 } } ], "vout": [ { "amount": 348424711391, "target": { "key": "28bb06343caf032d07af2b7dca728f6cdc57b2c949f2ec95b8d6c0bdffddd869" } } ], "extra": [ 1, 247, 197, 240, 66, 118, 166, 74, 106, 162, 87, 28, 52, 121, 20, 107, 61, 246, 74, 249, 13, 251, 210, 179, 45, 68, 242, 166, 125, 82, 101, 178, 121, 2, 17, 0, 0, 0, 172, 2, 107, 89, 243, 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