Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d75e075665378c06b8f59cba8592058363da563b594f509d0fca36c7d32ec611

Tx prefix hash: 71e8b7bbb0b655dc989c90740aa58f824da83bcc25864406d0422d734e8917d5
Tx public key: caec1547e9f1c88e4402dd1676cccc0bd4fcd99ae1e531e2e0dad52801da9362
Timestamp: 1734540906 Timestamp [UCT]: 2024-12-18 16:55:06 Age [y:d:h:m:s]: 00:330:20:20:54
Block: 1178027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233941 RingCT/type: yes/0
Extra: 01caec1547e9f1c88e4402dd1676cccc0bd4fcd99ae1e531e2e0dad52801da93620211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f579649e7f7b469be941d41402facd3ab9c9f1f29916eee6a4ee69516b00d0f 0.600000000000 1664410 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": 1178037, "vin": [ { "gen": { "height": 1178027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f579649e7f7b469be941d41402facd3ab9c9f1f29916eee6a4ee69516b00d0f" } } ], "extra": [ 1, 202, 236, 21, 71, 233, 241, 200, 142, 68, 2, 221, 22, 118, 204, 204, 11, 212, 252, 217, 154, 225, 229, 49, 226, 224, 218, 213, 40, 1, 218, 147, 98, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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