Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa1929aa15c4dded35f15f7c67752366b8d243ca1d3f5df0b21f5cc1832ed39

Tx prefix hash: e6fe4df0ee51a15492a27b92d997cb9b1a0b2619a237381f4a276cbf8542fadb
Tx public key: 04e897b5d7563ebf501144ca393908feb7167250c6deb1d7465f39e9b2172cec
Timestamp: 1675362829 Timestamp [UCT]: 2023-02-02 18:33:49 Age [y:d:h:m:s]: 02:111:04:13:45
Block: 688369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601121 RingCT/type: yes/0
Extra: 0104e897b5d7563ebf501144ca393908feb7167250c6deb1d7465f39e9b2172cec02110000000574b6d784000000000000000000

1 output(s) for total of 3.214753500000 dcy

stealth address amount amount idx
00: be889e0a63cdf46f0a6e2a4ccb9b28c42ea901328c49498270966b66d05d32e2 3.214753500000 1130981 of 0

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": 688379, "vin": [ { "gen": { "height": 688369 } } ], "vout": [ { "amount": 3214753500, "target": { "key": "be889e0a63cdf46f0a6e2a4ccb9b28c42ea901328c49498270966b66d05d32e2" } } ], "extra": [ 1, 4, 232, 151, 181, 215, 86, 62, 191, 80, 17, 68, 202, 57, 57, 8, 254, 183, 22, 114, 80, 198, 222, 177, 215, 70, 95, 57, 233, 178, 23, 44, 236, 2, 17, 0, 0, 0, 5, 116, 182, 215, 132, 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