Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d128ebd9442b0087e8b014bcf41e68643d33c5923f5f42ae5f89eacc84360b

Tx prefix hash: 27760337940a430f564eb11b44a2aa5b819d611751da2308b16c75dac5a83912
Tx public key: a0fa3e39db859ba737b823bd4c379c54e030013e99d0f5c8c20d957ccb429a30
Timestamp: 1579331994 Timestamp [UCT]: 2020-01-18 07:19:54 Age [y:d:h:m:s]: 04:340:17:05:34
Block: 47953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133159 RingCT/type: yes/0
Extra: 01a0fa3e39db859ba737b823bd4c379c54e030013e99d0f5c8c20d957ccb429a30021100000001dcee4b4d000000000000000000

1 output(s) for total of 425.708812739000 dcy

stealth address amount amount idx
00: fd5043d2d8b010b0170f68505d3cf3e8992e8dc3d0d34f059f70ccf7736122ef 425.708812739000 88692 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": 47963, "vin": [ { "gen": { "height": 47953 } } ], "vout": [ { "amount": 425708812739, "target": { "key": "fd5043d2d8b010b0170f68505d3cf3e8992e8dc3d0d34f059f70ccf7736122ef" } } ], "extra": [ 1, 160, 250, 62, 57, 219, 133, 155, 167, 55, 184, 35, 189, 76, 55, 156, 84, 224, 48, 1, 62, 153, 208, 245, 200, 194, 13, 149, 124, 203, 66, 154, 48, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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