Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 550ff86f188328c6c73790d084970e379dd7b50c907e2a43989bebe413795bd7

Tx prefix hash: 5f7995efbef8c90d1b4d7dcdbb16b9462072eb3143ba4f00894e2b4291e3adde
Tx public key: bcb380f027f7d9127898d5536feb1b19ab71dfb00ffcbe3896d3d696c3a869bc
Timestamp: 1577480109 Timestamp [UCT]: 2019-12-27 20:55:09 Age [y:d:h:m:s]: 05:159:07:24:18
Block: 33080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1263725 RingCT/type: yes/0
Extra: 01bcb380f027f7d9127898d5536feb1b19ab71dfb00ffcbe3896d3d696c3a869bc02110000019c78873133000000000000000000

1 output(s) for total of 476.870635930000 dcy

stealth address amount amount idx
00: 3f2adac8a8a41d820eb24b6e49925576029ed0a322ed5a018ad4ce807929bae0 476.870635930000 55227 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": 33090, "vin": [ { "gen": { "height": 33080 } } ], "vout": [ { "amount": 476870635930, "target": { "key": "3f2adac8a8a41d820eb24b6e49925576029ed0a322ed5a018ad4ce807929bae0" } } ], "extra": [ 1, 188, 179, 128, 240, 39, 247, 217, 18, 120, 152, 213, 83, 111, 235, 27, 25, 171, 113, 223, 176, 15, 252, 190, 56, 150, 211, 214, 150, 195, 168, 105, 188, 2, 17, 0, 0, 1, 156, 120, 135, 49, 51, 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