Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd16d9625855d45624f0b770319c0d80b1b7ae15cf5a9fe1e656d51b12ae778b

Tx prefix hash: 2c6fdd881fe0e80eed2ceff1113c8d04bafab30d5694f18ae9fd0f29c679b2d0
Tx public key: 797dac47112ce5dee1b1f1df3ddcd406912e8f77b752b5dadd7a0e7a4cf1bdad
Timestamp: 1587535716 Timestamp [UCT]: 2020-04-22 06:08:36 Age [y:d:h:m:s]: 05:019:07:58:00
Block: 94854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185067 RingCT/type: yes/0
Extra: 01797dac47112ce5dee1b1f1df3ddcd406912e8f77b752b5dadd7a0e7a4cf1bdad021100000006d81c26c0000000000000000000

1 output(s) for total of 297.652881128000 dcy

stealth address amount amount idx
00: 131057890eef774f9c5ec439c72155637db26cbace7daaca9220469b3e4b83f7 297.652881128000 168722 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": 94864, "vin": [ { "gen": { "height": 94854 } } ], "vout": [ { "amount": 297652881128, "target": { "key": "131057890eef774f9c5ec439c72155637db26cbace7daaca9220469b3e4b83f7" } } ], "extra": [ 1, 121, 125, 172, 71, 17, 44, 229, 222, 225, 177, 241, 223, 61, 220, 212, 6, 145, 46, 143, 119, 183, 82, 181, 218, 221, 122, 14, 122, 76, 241, 189, 173, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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