Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a0524abf9f336423ba38b7ce02a644152992102e086b0a13cc1206ab7413dac

Tx prefix hash: cf13383b76cb0d82dd80dcf9a745c8aea9eb3af7a83a0f7c75982393bda49091
Tx public key: 3b1d2d69153b962467f1af27598bf7bca144502e854588e415a0515fae740aed
Timestamp: 1722090539 Timestamp [UCT]: 2024-07-27 14:28:59 Age [y:d:h:m:s]: 00:306:14:41:21
Block: 1074882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219091 RingCT/type: yes/0
Extra: 013b1d2d69153b962467f1af27598bf7bca144502e854588e415a0515fae740aed02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6dcdfca6316f12e3bd4f0c0cfaf1ae9a6fabd6f65f70a1cda5173b8dca02986 0.600000000000 1547401 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": 1074892, "vin": [ { "gen": { "height": 1074882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6dcdfca6316f12e3bd4f0c0cfaf1ae9a6fabd6f65f70a1cda5173b8dca02986" } } ], "extra": [ 1, 59, 29, 45, 105, 21, 59, 150, 36, 103, 241, 175, 39, 89, 139, 247, 188, 161, 68, 80, 46, 133, 69, 136, 228, 21, 160, 81, 95, 174, 116, 10, 237, 2, 17, 0, 0, 0, 15, 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