Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6b94ab1568c512d525c5c0cddb976b6f2fe7351746e0241f04af7cb4a57877a

Tx prefix hash: ee9a3e58796442454abd2d00c6a1b0c7e82780bbf403c0f36aa3c95d50ba870d
Tx public key: 50d5cfb8affd728d140076ed23a74b8ef288c1f3780092a7aff61aa437f4e758
Timestamp: 1649060402 Timestamp [UCT]: 2022-04-04 08:20:02 Age [y:d:h:m:s]: 02:316:14:48:10
Block: 472868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745819 RingCT/type: yes/0
Extra: 0150d5cfb8affd728d140076ed23a74b8ef288c1f3780092a7aff61aa437f4e758021100000008cb8520c2000000000000000000

1 output(s) for total of 16.641492148000 dcy

stealth address amount amount idx
00: 7a35ac51f573afba0e2733fc8668b5d8b78461d4931560aab161c646fcd9ea01 16.641492148000 892567 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": 472878, "vin": [ { "gen": { "height": 472868 } } ], "vout": [ { "amount": 16641492148, "target": { "key": "7a35ac51f573afba0e2733fc8668b5d8b78461d4931560aab161c646fcd9ea01" } } ], "extra": [ 1, 80, 213, 207, 184, 175, 253, 114, 141, 20, 0, 118, 237, 35, 167, 75, 142, 242, 136, 193, 243, 120, 0, 146, 167, 175, 246, 26, 164, 55, 244, 231, 88, 2, 17, 0, 0, 0, 8, 203, 133, 32, 194, 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