Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5270f75856cd9f33e81f73efd2136391fedcf3e87f9a128227893099c1b4ea

Tx prefix hash: 70e8f2fa1ca572af4cbe05e5188efee451ecfb772cf164e00773c398b4a63ce4
Tx public key: 4e29d122c3a773f3ca402b4431f8cb49d8db606987aea914d3e4a05c164dbebf
Timestamp: 1704175509 Timestamp [UCT]: 2024-01-02 06:05:09 Age [y:d:h:m:s]: 01:086:21:05:12
Block: 926356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323199 RingCT/type: yes/0
Extra: 014e29d122c3a773f3ca402b4431f8cb49d8db606987aea914d3e4a05c164dbebf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b2ef4dd90617bcd980f2d06acd355043090be8ff58863a7864696c3ed119ce1 0.600000000000 1384138 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": 926366, "vin": [ { "gen": { "height": 926356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b2ef4dd90617bcd980f2d06acd355043090be8ff58863a7864696c3ed119ce1" } } ], "extra": [ 1, 78, 41, 209, 34, 195, 167, 115, 243, 202, 64, 43, 68, 49, 248, 203, 73, 216, 219, 96, 105, 135, 174, 169, 20, 211, 228, 160, 92, 22, 77, 190, 191, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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