Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7e190ff86692356912ee261f2305c4e77e889d2a817011ae9031909728c09d

Tx prefix hash: d2855189618716250e1d429d7b05dcda079d4f8a6cda706ba6a8b983a95519b2
Tx public key: d5dd89c775f8d036109f2f1f30a4f1661eec794a69893bbd99bfeadd46c5aedd
Timestamp: 1707966983 Timestamp [UCT]: 2024-02-15 03:16:23 Age [y:d:h:m:s]: 01:055:02:56:14
Block: 957786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300442 RingCT/type: yes/0
Extra: 01d5dd89c775f8d036109f2f1f30a4f1661eec794a69893bbd99bfeadd46c5aedd0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa6e1553f81a129198e13377869a5375af542bb7221f108b5f54fd66bdc06847 0.600000000000 1417137 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": 957796, "vin": [ { "gen": { "height": 957786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa6e1553f81a129198e13377869a5375af542bb7221f108b5f54fd66bdc06847" } } ], "extra": [ 1, 213, 221, 137, 199, 117, 248, 208, 54, 16, 159, 47, 31, 48, 164, 241, 102, 30, 236, 121, 74, 105, 137, 59, 189, 153, 191, 234, 221, 70, 197, 174, 221, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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