Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d042be5e53303f6103262125dcbfcfbfd1f7990990da247ecd59ec50c21582ec

Tx prefix hash: 651bdcd71b1f40f613a54af8cdca2dff29d22b8206f6e80b91e08977c5795ba1
Tx public key: cb7daeb638d02c2695c5f51d79ebf6c6eecdbb2e00e19de3469a9f9185dcad08
Timestamp: 1588514040 Timestamp [UCT]: 2020-05-03 13:54:00 Age [y:d:h:m:s]: 05:026:15:10:25
Block: 97925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195335 RingCT/type: yes/0
Extra: 01cb7daeb638d02c2695c5f51d79ebf6c6eecdbb2e00e19de3469a9f9185dcad08021100000003209b4bc8000000000000000000

1 output(s) for total of 290.759952573000 dcy

stealth address amount amount idx
00: 63fe9f3e9e2a20dc5dd162c1657f388711da2d1734e732d2df8c882379b2e56c 290.759952573000 173252 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": 97935, "vin": [ { "gen": { "height": 97925 } } ], "vout": [ { "amount": 290759952573, "target": { "key": "63fe9f3e9e2a20dc5dd162c1657f388711da2d1734e732d2df8c882379b2e56c" } } ], "extra": [ 1, 203, 125, 174, 182, 56, 208, 44, 38, 149, 197, 245, 29, 121, 235, 246, 198, 238, 205, 187, 46, 0, 225, 157, 227, 70, 154, 159, 145, 133, 220, 173, 8, 2, 17, 0, 0, 0, 3, 32, 155, 75, 200, 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