Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bacde76b93a0ae16925af6c67584921f7abd6c1f0b63fc65e06604ec6fd616c6

Tx prefix hash: d2eac93026c48547da15b750239734564385c454e642700d4345a1217b04fa62
Tx public key: 0b9f7a031abc97e36b17d5ad282b413a766b8c0bda70491ddcf140b4fd7b4789
Timestamp: 1705239570 Timestamp [UCT]: 2024-01-14 13:39:30 Age [y:d:h:m:s]: 00:362:16:43:13
Block: 935175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259677 RingCT/type: yes/0
Extra: 010b9f7a031abc97e36b17d5ad282b413a766b8c0bda70491ddcf140b4fd7b47890211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566f14567ff067f394e7e83fd693591724540bde69a2c3355ba62de1a5575e75 0.600000000000 1393191 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": 935185, "vin": [ { "gen": { "height": 935175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566f14567ff067f394e7e83fd693591724540bde69a2c3355ba62de1a5575e75" } } ], "extra": [ 1, 11, 159, 122, 3, 26, 188, 151, 227, 107, 23, 213, 173, 40, 43, 65, 58, 118, 107, 140, 11, 218, 112, 73, 29, 220, 241, 64, 180, 253, 123, 71, 137, 2, 17, 0, 0, 0, 3, 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