Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e189d6d22f8c9476187d49146a0087d7f1abdbd6dac7495390533529167f3af

Tx prefix hash: 805134f532b212d37f9c691f95a0c36b8b10756d8ecc66c84e406ea705be1a15
Tx public key: dd0fe71954451b0208ab5e016b0c44bc1d6bac0d938510308fa0d66319443bc2
Timestamp: 1580768507 Timestamp [UCT]: 2020-02-03 22:21:47 Age [y:d:h:m:s]: 05:016:03:07:45
Block: 57939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163642 RingCT/type: yes/0
Extra: 01dd0fe71954451b0208ab5e016b0c44bc1d6bac0d938510308fa0d66319443bc202110000001b4943cd9f000000000000000000

1 output(s) for total of 394.479884829000 dcy

stealth address amount amount idx
00: 03e1edcf1d7066619c0b0ae0f055b2b34da6978cbcced1de92743121af6f6db6 394.479884829000 107150 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": 57949, "vin": [ { "gen": { "height": 57939 } } ], "vout": [ { "amount": 394479884829, "target": { "key": "03e1edcf1d7066619c0b0ae0f055b2b34da6978cbcced1de92743121af6f6db6" } } ], "extra": [ 1, 221, 15, 231, 25, 84, 69, 27, 2, 8, 171, 94, 1, 107, 12, 68, 188, 29, 107, 172, 13, 147, 133, 16, 48, 143, 160, 214, 99, 25, 68, 59, 194, 2, 17, 0, 0, 0, 27, 73, 67, 205, 159, 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