Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5106df5c6e31b4a93e7d95f9c9bac66ac058b32ba3e1b4ef27e0e935bacfc6

Tx prefix hash: 4e257cd2d8afe25e91787af7528384c8098b27abaa3c5dbaa3e9d8255eb5797f
Tx public key: 9028540c72e432cce30854308e8cefd0d0282aefede9f0fbe13fbbb3da757962
Timestamp: 1715020657 Timestamp [UCT]: 2024-05-06 18:37:37 Age [y:d:h:m:s]: 00:350:23:27:09
Block: 1016280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250885 RingCT/type: yes/0
Extra: 019028540c72e432cce30854308e8cefd0d0282aefede9f0fbe13fbbb3da7579620211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abfca869a18d783c6697510d2f9bf5fe622f7d611853a55b9fbe88e4c4b0621f 0.600000000000 1479815 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": 1016290, "vin": [ { "gen": { "height": 1016280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abfca869a18d783c6697510d2f9bf5fe622f7d611853a55b9fbe88e4c4b0621f" } } ], "extra": [ 1, 144, 40, 84, 12, 114, 228, 50, 204, 227, 8, 84, 48, 142, 140, 239, 208, 208, 40, 42, 239, 237, 233, 240, 251, 225, 63, 187, 179, 218, 117, 121, 98, 2, 17, 0, 0, 0, 2, 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