Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12cce03987dc2b84f49b21608dc5863c347a1334b9b9d524b65685955e4b935b

Tx prefix hash: df7d8fd253c08bcb9dd0c60a3a8d92f7898b9fb8e616145f3b0d11f5bc441086
Tx public key: e2f7cc653efafff586cd725bd543196f652a589c7ab30a17e89d34ce7bfaa0df
Timestamp: 1721279384 Timestamp [UCT]: 2024-07-18 05:09:44 Age [y:d:h:m:s]: 00:129:02:27:50
Block: 1068177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92364 RingCT/type: yes/0
Extra: 01e2f7cc653efafff586cd725bd543196f652a589c7ab30a17e89d34ce7bfaa0df02110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76c0a9d12e5f9be4ccbe9abd1c060ed0dca106eb24dc934716255a790832608 0.600000000000 1539222 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": 1068187, "vin": [ { "gen": { "height": 1068177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76c0a9d12e5f9be4ccbe9abd1c060ed0dca106eb24dc934716255a790832608" } } ], "extra": [ 1, 226, 247, 204, 101, 62, 250, 255, 245, 134, 205, 114, 91, 213, 67, 25, 111, 101, 42, 88, 156, 122, 179, 10, 23, 232, 157, 52, 206, 123, 250, 160, 223, 2, 17, 0, 0, 0, 20, 145, 225, 60, 4, 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