Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc0963ecd4340a3a1edd4deea06e81a1c0c8588b8204791770f049582fdbb15b

Tx prefix hash: ebc95bd58471cc5cb029a5967c4d4332795d0abbe3ff630bc699c6358d0ab5ad
Tx public key: db31dfb02142c64e4c29af10ed2bb68836e364fe26f117053a05821184f9c66c
Timestamp: 1581946380 Timestamp [UCT]: 2020-02-17 13:33:00 Age [y:d:h:m:s]: 04:262:14:49:37
Block: 66653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080184 RingCT/type: yes/0
Extra: 01db31dfb02142c64e4c29af10ed2bb68836e364fe26f117053a05821184f9c66c02110000000112c4732d000000000000000000

1 output(s) for total of 369.106548765000 dcy

stealth address amount amount idx
00: 0f57f318ada18022c883932cf4b7283584b4cadf1c563c19bdce4a943e1f0cb1 369.106548765000 122810 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": 66663, "vin": [ { "gen": { "height": 66653 } } ], "vout": [ { "amount": 369106548765, "target": { "key": "0f57f318ada18022c883932cf4b7283584b4cadf1c563c19bdce4a943e1f0cb1" } } ], "extra": [ 1, 219, 49, 223, 176, 33, 66, 198, 78, 76, 41, 175, 16, 237, 43, 182, 136, 54, 227, 100, 254, 38, 241, 23, 5, 58, 5, 130, 17, 132, 249, 198, 108, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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