Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d5c4e21a1865e23ff5b54e8bedbe47a530425ca7e1f88c849e0f569b8cfc59

Tx prefix hash: 27c39a69bea678a2ffe3122b5a36d4ba404660d1c9390254468f845dec3a1e5b
Tx public key: ac1a63bffd10d098133526edd1c6d74286d665d5fa75e5433deda8219d796e8b
Timestamp: 1731966109 Timestamp [UCT]: 2024-11-18 21:41:49 Age [y:d:h:m:s]: 01:033:12:39:16
Block: 1156658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282423 RingCT/type: yes/0
Extra: 01ac1a63bffd10d098133526edd1c6d74286d665d5fa75e5433deda8219d796e8b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b428f54e1fb6d3963b8abc6a38caf60219712052bff358be65a05f3f295ae8 0.600000000000 1642281 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": 1156668, "vin": [ { "gen": { "height": 1156658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b428f54e1fb6d3963b8abc6a38caf60219712052bff358be65a05f3f295ae8" } } ], "extra": [ 1, 172, 26, 99, 191, 253, 16, 208, 152, 19, 53, 38, 237, 209, 198, 215, 66, 134, 214, 101, 213, 250, 117, 229, 67, 61, 237, 168, 33, 157, 121, 110, 139, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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