Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d8b3a3feb593cb8511d7ed4ade0f1062e1853124194b87880b8ddc41dc238f

Tx prefix hash: 577caa06d1a82121900d8f7cb33f3bc0f891dc999ba4e3628263f4e2d9f418fe
Tx public key: 8875ccc25350c9c3ad96e2fe5995a012f6b6677da8df89001f798bba5f8d57f2
Timestamp: 1583239460 Timestamp [UCT]: 2020-03-03 12:44:20 Age [y:d:h:m:s]: 05:089:16:30:53
Block: 75721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1218974 RingCT/type: yes/0
Extra: 018875ccc25350c9c3ad96e2fe5995a012f6b6677da8df89001f798bba5f8d57f202110000011512c4732d000000000000000000

1 output(s) for total of 344.433741983000 dcy

stealth address amount amount idx
00: 32d19a03c1f5e31248f59e2cb81b99ca3387e3e144f6895e9e203e26bec100d5 344.433741983000 139691 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": 75731, "vin": [ { "gen": { "height": 75721 } } ], "vout": [ { "amount": 344433741983, "target": { "key": "32d19a03c1f5e31248f59e2cb81b99ca3387e3e144f6895e9e203e26bec100d5" } } ], "extra": [ 1, 136, 117, 204, 194, 83, 80, 201, 195, 173, 150, 226, 254, 89, 149, 160, 18, 246, 182, 103, 125, 168, 223, 137, 0, 31, 121, 139, 186, 95, 141, 87, 242, 2, 17, 0, 0, 1, 21, 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