Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 837c0dfcef79c7c6a78e8814552206a7237bc3a56342621de82231aa98c3349d

Tx prefix hash: fc098752737596d3cbdd148a1bb6cb420666b2dfa1c42f52143aa415d5f5e2e4
Tx public key: 43a29da1533b9abae5278037f2a105ae27c4af769b1fef17f1bfc358410e0e9e
Timestamp: 1639016190 Timestamp [UCT]: 2021-12-09 02:16:30 Age [y:d:h:m:s]: 03:186:21:15:44
Block: 391474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 912307 RingCT/type: yes/0
Extra: 0143a29da1533b9abae5278037f2a105ae27c4af769b1fef17f1bfc358410e0e9e021100000001e9564d6f000000000000000000

1 output(s) for total of 30.973156069000 dcy

stealth address amount amount idx
00: 9d07abe3bbfabf57529a9bbf3d23945a1a4e31201e7d872c107dfb01db94a55c 30.973156069000 787881 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": 391484, "vin": [ { "gen": { "height": 391474 } } ], "vout": [ { "amount": 30973156069, "target": { "key": "9d07abe3bbfabf57529a9bbf3d23945a1a4e31201e7d872c107dfb01db94a55c" } } ], "extra": [ 1, 67, 162, 157, 161, 83, 59, 154, 186, 229, 39, 128, 55, 242, 161, 5, 174, 39, 196, 175, 118, 155, 31, 239, 23, 241, 191, 195, 88, 65, 14, 14, 158, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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