Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 157d1a32fc4857130e9af669cea43329330f43f2b6a57a8ac426a29a1b767eb0

Tx prefix hash: ca0ad81a5690c7b3bda3c6c4a7695720a1aeb9977b228631f8d962d0f332eeb0
Tx public key: af1e0b8641b26d78556799adbc0c963c0a8b04757aed10e2f1d6e54514ab0db9
Timestamp: 1725029368 Timestamp [UCT]: 2024-08-30 14:49:28 Age [y:d:h:m:s]: 00:225:15:30:26
Block: 1099242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161131 RingCT/type: yes/0
Extra: 01af1e0b8641b26d78556799adbc0c963c0a8b04757aed10e2f1d6e54514ab0db902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcc03f645083392876c810003aa384e4769d06b0cd3a7fda2ac42dfbf8b22450 0.600000000000 1575189 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": 1099252, "vin": [ { "gen": { "height": 1099242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc03f645083392876c810003aa384e4769d06b0cd3a7fda2ac42dfbf8b22450" } } ], "extra": [ 1, 175, 30, 11, 134, 65, 178, 109, 120, 85, 103, 153, 173, 188, 12, 150, 60, 10, 139, 4, 117, 122, 237, 16, 226, 241, 214, 229, 69, 20, 171, 13, 185, 2, 17, 0, 0, 0, 5, 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