Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd67049840ec71787d00b756108e3d2311cf5e30df1172adf7cd94f4e0ad2e7

Tx prefix hash: 6cd10da3f9a3f276df451fb5226ddfa4cbe50ec6e6d7ca231b953c24900e5bb0
Tx public key: 16ea3f50fb0a16ebbe4a2d13cce1ea1f8cad1ac984d3d0c600d53a41b2b6bed1
Timestamp: 1702661989 Timestamp [UCT]: 2023-12-15 17:39:49 Age [y:d:h:m:s]: 01:157:03:30:43
Block: 913811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373486 RingCT/type: yes/0
Extra: 0116ea3f50fb0a16ebbe4a2d13cce1ea1f8cad1ac984d3d0c600d53a41b2b6bed102110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af32fbd71b21c378cdbb52058a3312007f695bbe0b0c5f1687dc9f727bdadbcf 0.600000000000 1371091 of 15

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": 913821, "vin": [ { "gen": { "height": 913811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af32fbd71b21c378cdbb52058a3312007f695bbe0b0c5f1687dc9f727bdadbcf" } } ], "extra": [ 1, 22, 234, 63, 80, 251, 10, 22, 235, 190, 74, 45, 19, 204, 225, 234, 31, 140, 173, 26, 201, 132, 211, 208, 198, 0, 213, 58, 65, 178, 182, 190, 209, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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