Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7361bb1ee3bb8720418be20cbc7cfbead38d4a423af7509c43db16323ab41dc

Tx prefix hash: c0a3b24a62ede9a45e0a054aea69ae41777cf01e0ee1593fa9b6f6e3276acec3
Tx public key: 435a4b0a1d74bb57f14b7c7c8968f0e5650935f5fccecb7387438338ca8ee01a
Timestamp: 1636889030 Timestamp [UCT]: 2021-11-14 11:23:50 Age [y:d:h:m:s]: 03:120:17:05:03
Block: 374136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864747 RingCT/type: yes/0
Extra: 01435a4b0a1d74bb57f14b7c7c8968f0e5650935f5fccecb7387438338ca8ee01a02110000000137cb3088000000000000000000

1 output(s) for total of 35.345368105000 dcy

stealth address amount amount idx
00: 05a886c3185e943672cfa45cf6b02b31392b1234f83d753092a9de95e91cbda5 35.345368105000 757410 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": 374146, "vin": [ { "gen": { "height": 374136 } } ], "vout": [ { "amount": 35345368105, "target": { "key": "05a886c3185e943672cfa45cf6b02b31392b1234f83d753092a9de95e91cbda5" } } ], "extra": [ 1, 67, 90, 75, 10, 29, 116, 187, 87, 241, 75, 124, 124, 137, 104, 240, 229, 101, 9, 53, 245, 252, 206, 203, 115, 135, 67, 131, 56, 202, 142, 224, 26, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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