Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e85a8fd1d24a09a87bb0d3a2503e55caeb0f06b435e7ae98b0b64c37104205a

Tx prefix hash: 23fd1c37e02eeba42bbeba6ab0ceaabbed2f3beb3a4dd767dbd85d0c2457a242
Tx public key: 8bd6a60985ea533ff097723c61b08d0943afd4b1897ec5854db312c6270bb91e
Timestamp: 1722199160 Timestamp [UCT]: 2024-07-28 20:39:20 Age [y:d:h:m:s]: 00:280:16:46:18
Block: 1075784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200543 RingCT/type: yes/0
Extra: 018bd6a60985ea533ff097723c61b08d0943afd4b1897ec5854db312c6270bb91e02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cc2ce89db1aa29cb142dad1ddd2f803de43c64658071b0aa5e6c40d559ace59 0.600000000000 1548313 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": 1075794, "vin": [ { "gen": { "height": 1075784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cc2ce89db1aa29cb142dad1ddd2f803de43c64658071b0aa5e6c40d559ace59" } } ], "extra": [ 1, 139, 214, 166, 9, 133, 234, 83, 63, 240, 151, 114, 60, 97, 176, 141, 9, 67, 175, 212, 177, 137, 126, 197, 133, 77, 179, 18, 198, 39, 11, 185, 30, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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