Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739ae751734550d5f31b80fd3614f84d5125de459e5a544dc985a2aa22e672c6

Tx prefix hash: 016c4e2190f586d3342d2b67fc2f4989413a39197c5af6e40cc7c1a26aa10ad7
Tx public key: a3bfd98b3c58d27290619076f30db217786e9595153a39adf7ff6515920f8cfa
Timestamp: 1576133347 Timestamp [UCT]: 2019-12-12 06:49:07 Age [y:d:h:m:s]: 05:143:04:24:38
Block: 26067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248051 RingCT/type: yes/0
Extra: 01a3bfd98b3c58d27290619076f30db217786e9595153a39adf7ff6515920f8cfa0211000000169159db1e000000000000000000

1 output(s) for total of 503.071919031000 dcy

stealth address amount amount idx
00: cbede75b6a5aa841a2f3e2fb5c48bf5080a25eb1650c888b56fbbbf8fcbcec7f 503.071919031000 43022 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": 26077, "vin": [ { "gen": { "height": 26067 } } ], "vout": [ { "amount": 503071919031, "target": { "key": "cbede75b6a5aa841a2f3e2fb5c48bf5080a25eb1650c888b56fbbbf8fcbcec7f" } } ], "extra": [ 1, 163, 191, 217, 139, 60, 88, 210, 114, 144, 97, 144, 118, 243, 13, 178, 23, 120, 110, 149, 149, 21, 58, 57, 173, 247, 255, 101, 21, 146, 15, 140, 250, 2, 17, 0, 0, 0, 22, 145, 89, 219, 30, 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