Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634f72bde69bc92e2d9dc78f126fcec613630875ef9d1daef3475d0f7ff47a12

Tx prefix hash: d53f7d3303f55b43a3f229669e25dea742d244c67e0abeb95a95cfe26fe645d5
Tx public key: 53070fb01d1c22c5b6b8c607ce444b7d00fe03f4e16cbcf3e3c329ed7449d0ba
Timestamp: 1583637515 Timestamp [UCT]: 2020-03-08 03:18:35 Age [y:d:h:m:s]: 04:296:15:58:28
Block: 78437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106772 RingCT/type: yes/0
Extra: 0153070fb01d1c22c5b6b8c607ce444b7d00fe03f4e16cbcf3e3c329ed7449d0ba02110000000ce89b4e54000000000000000000

1 output(s) for total of 337.369991726000 dcy

stealth address amount amount idx
00: 1a3090aef2b0b1d2c543d00a5e39de858e6da42d80ec2cc6fc21f4a24b1aef06 337.369991726000 143891 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": 78447, "vin": [ { "gen": { "height": 78437 } } ], "vout": [ { "amount": 337369991726, "target": { "key": "1a3090aef2b0b1d2c543d00a5e39de858e6da42d80ec2cc6fc21f4a24b1aef06" } } ], "extra": [ 1, 83, 7, 15, 176, 29, 28, 34, 197, 182, 184, 198, 7, 206, 68, 75, 125, 0, 254, 3, 244, 225, 108, 188, 243, 227, 195, 41, 237, 116, 73, 208, 186, 2, 17, 0, 0, 0, 12, 232, 155, 78, 84, 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