Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aca65840b44e7dd7eac8c8fc28c43a613cafc820a4dd7a05f88dec063a61388

Tx prefix hash: b032fcf56e43812fdecc44c002fa89b90afb4fe84440c6396740bb64ca154f84
Tx public key: 7e8b48bb6358b776e3e8d6433c8508133d6b2e675f4d47a103ce4e6ab05b6d7a
Timestamp: 1725002044 Timestamp [UCT]: 2024-08-30 07:14:04 Age [y:d:h:m:s]: 00:231:00:06:04
Block: 1099023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164964 RingCT/type: yes/0
Extra: 017e8b48bb6358b776e3e8d6433c8508133d6b2e675f4d47a103ce4e6ab05b6d7a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e2c86cddd3cc74b0f6290e93ca7cace0c39db7b18549269c09e7fbb47859e58 0.600000000000 1574940 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": 1099033, "vin": [ { "gen": { "height": 1099023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e2c86cddd3cc74b0f6290e93ca7cace0c39db7b18549269c09e7fbb47859e58" } } ], "extra": [ 1, 126, 139, 72, 187, 99, 88, 183, 118, 227, 232, 214, 67, 60, 133, 8, 19, 61, 107, 46, 103, 95, 77, 71, 161, 3, 206, 78, 106, 176, 91, 109, 122, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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