Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6437422fb11b91f0d8d3efa40c11836e36f8ca79036c271f15e2d67cbfb1ccf

Tx prefix hash: 995b2670bd4a7eded734ab7b0ef51f9cde1fb3dcc670d50ab62b8114517610de
Tx public key: 914d147a8a9ef565f41fb4d87e38ce3133f7b89cb57030c500f56ab7023b4726
Timestamp: 1674800463 Timestamp [UCT]: 2023-01-27 06:21:03 Age [y:d:h:m:s]: 02:094:05:29:23
Block: 683709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589009 RingCT/type: yes/0
Extra: 01914d147a8a9ef565f41fb4d87e38ce3133f7b89cb57030c500f56ab7023b47260211000000045029cbac000000000000000000

1 output(s) for total of 3.331104054000 dcy

stealth address amount amount idx
00: 71369d3c282969346a3f6ce76c978c189ed96545c8164b913b7fdfb292f9cb3e 3.331104054000 1125908 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": 683719, "vin": [ { "gen": { "height": 683709 } } ], "vout": [ { "amount": 3331104054, "target": { "key": "71369d3c282969346a3f6ce76c978c189ed96545c8164b913b7fdfb292f9cb3e" } } ], "extra": [ 1, 145, 77, 20, 122, 138, 158, 245, 101, 244, 31, 180, 216, 126, 56, 206, 49, 51, 247, 184, 156, 181, 112, 48, 197, 0, 245, 106, 183, 2, 59, 71, 38, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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