Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7f69ea3dc9521f93d45324758f2d3085e53930082259524ced30fa06a023b2

Tx prefix hash: c779639ea8db4f2ce20c890c45f81eb870380ab2caa94c5a33ff5bcfcc76990b
Tx public key: 5c09f9419adfa997b19b0c2f4623cdfc29aa76901d2c25bfff5f6630fff3b17d
Timestamp: 1581965269 Timestamp [UCT]: 2020-02-17 18:47:49 Age [y:d:h:m:s]: 04:315:18:56:48
Block: 67000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118037 RingCT/type: yes/0
Extra: 015c09f9419adfa997b19b0c2f4623cdfc29aa76901d2c25bfff5f6630fff3b17d0211000000174ac5aa02000000000000000000

1 output(s) for total of 368.130664749000 dcy

stealth address amount amount idx
00: 6951545f096a96c8ffc57e9e117f6e82123179afc67da0a04f3bbde6482a9985 368.130664749000 123381 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": 67010, "vin": [ { "gen": { "height": 67000 } } ], "vout": [ { "amount": 368130664749, "target": { "key": "6951545f096a96c8ffc57e9e117f6e82123179afc67da0a04f3bbde6482a9985" } } ], "extra": [ 1, 92, 9, 249, 65, 154, 223, 169, 151, 177, 155, 12, 47, 70, 35, 205, 252, 41, 170, 118, 144, 29, 44, 37, 191, 255, 95, 102, 48, 255, 243, 177, 125, 2, 17, 0, 0, 0, 23, 74, 197, 170, 2, 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